XOOPS 
Forum
Forum Index General Forums Community Support Modules Support Themes Support Development International Support Module Hack Reviews Theme Designer Talk


« 1 ... 17 18 19 (20) 21 »


191
Daigoro
Re: SOLVED - Making Xoops CONTENT Multilingual

  • 2003/10/7 22:29

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


mCity,

Thanks for sharing!


mCity wrote:
Quote:

Well, I hope XOOPS would add this square backet method to core even if they implement XOOPS multilingual by adding an extra column for language to related tables. We don't need to have extra column for blocks titles. We need news, comment, and forum content, etc for members to use. For admin, I prefer to use this way still: "Select [tch]English[/tch][eng]Chinese[/eng]" for assign title to select language block and most place.


I agree it's a convinient method, IF you happen to know all the languages. I'm webmaster on a danish, japanese and english site, and often I have problems remembering the japanese words - thus other people need to edit the text again, with the risk of axidental mistakes happening in the other languages. Now imagine supporting 20 languages or more, perhaps having 10 or 15 people going thru all the lines to insert/translate their part. It's a hell.

mCity wrote:
Quote:

Today, I solved the way to show in blocks administration table.

edit /modules/system/admin/blocksadmin/blocksadmin.php in function list_blocks(line 41)
Quote:
global $xoopsUser, $xoopsConfig, $myts, $HTTP_GET_VARS;



Great work. I did however have problems with the above line.
Instead of that line, I added the following as a new line 42:

Quote:
$myts =& MyTextSanitizer::getInstance();


All the other lines worked as they should.

I noticed that things like custom blocks, which don't belong to a module will have a name as an unbreabable space:
Quote:
 
- couldn't (within a few minutes) find out how to change it to be nothing.

I also noticed the drop-down box isn't fixed yet.


All in all. Good work!

Topic | Forum


192
Daigoro
Re: SOLVED - Making Xoops CONTENT Multilingual

  • 2003/10/7 10:11

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


ibzan,

You are right, something ought to be though out. And I belive the core team is thinking/working on a solution.
However, until an universal solution has been implemented, this kind of hacking is needed.

I must admit that I realy like using squre brackets to select the language "on the fly", eg. when writing a message. But on other ocations, it's a pain to use!
I'd like to see it implemented in the core, TOGETHER with a system to manage multiple languages.

I don't belive it's possible to make an automatic system that will enable all modules to be multilangual. The modules will need to be written to support it.
Topic | Forum


193
Daigoro
Re: Problem with Xoops memberlist in Opera

  • 2003/10/7 9:55

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


Quote:

onokazu wrote:
This has been fixed in XOOPS 2.0.5 RC


Great. Thanks!

I'm now running a heavily hacked XOOPS system, and would prefer to postpone upgrading as long as possible. Can I just install the new memberlist module in the old system?
Topic | Forum


194
Daigoro
Problem with Xoops memberlist in Opera

  • 2003/10/5 19:19

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


Several of my users has complained about not beeing able to use the memberlist on their Opera browsers.

The problem appears after the membersearch, when the first list of members is beeing displayed. To see the next part of list, one have to press "2", "3" etc.. This is where Opera breaks, as it returns the user directly to the search form.

I looked thrugh the memberlist php code, and noticed an interesting feature, which I haven't seen any other place.
When pressing "2", the URL is set to "modules/xoopsmembers/index.php#2", and the "#2" part is used inside the module to display part 2 of the list.
However, it seems Opera belives a hash (#) indicates an onpage referance to be evaluated after the page is recieved, and thus should not be forwarded to the server.
In other words, "modules/xoopsmembers/index.php#2" is sent to the server as "modules/xoopsmembers/index.php".

I guess the source should be modified to use "?" instead of "#", but I'm not realy good enough at php to do it.

Did any of you allready make this fix?

Best regards,
Topic | Forum


195
Daigoro
Re: Is anyone interested ine a Genealogy Module for Xoops2?

  • 2003/8/20 14:02

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


Rcrong,
I don't belive there are any real genealogy module available for Xoops2. Sofar the only related module I have been able to find is a GEDCOM viewer at http://www.poplargedcomviewer.com/modules/mydownloads/singlefile.php?lid=10

My mother would be very happy if I could provide her with online genealogy functionality. Thus I'm very interested having a genealogy module for Xoops2. I'm afraide I can't help porting it, but I would be happy to help testing it.
Topic | Forum


196
Daigoro
Re: SOLVED - Making Xoops CONTENT Multilingual *Fixed Code Quote problem*

  • 2003/8/5 17:52

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


Finaly I figured out where the site name of the titleline was inserted into the site. Just as with the Slogan, it's in the header.php file.

The title line is divided into two parts:
The first part is the site name, set using the admin->preferances->general settings form.
The second part is a slogan which changes for each module you enter - and for the startpage is is set in same place as the site name.

In a previous posting in this thread, I explained the four placed I changed to change the slogan. I at the time that two of the four changes would cover the site name and the other two would cover the slogan - not so!

In order to change the site name, I replaced the following line
$xoopsTpl->assign(array('xoops_theme' => $xoopsConfig['theme_set'], 'xoops_imageurl' => XOOPS_URL.'/themes/'.$xoopsConfig['theme_set'].'/', 'xoops_themecss'=> xoops_getcss($xoopsConfig['theme_set']), 'xoops_requesturi' => htmlspecialchars($GLOBALS['xoopsRequestUri'], ENT_QUOTES), 'xoops_sitename' => $xoopsConfig['sitename'], 'xoops_slogan' => $xoopsConfig['slogan']));


...with the following lines

$myts =& MyTextSanitizer::getInstance();
$xoopsTpl->assign(array('xoops_theme' => $xoopsConfig['theme_set'], 'xoops_imageurl' => XOOPS_URL.'/themes/'.$xoopsConfig['theme_set'].'/', 'xoops_themecss'=> xoops_getcss($xoopsConfig['theme_set']), 'xoops_requesturi' => htmlspecialchars($GLOBALS['xoopsRequestUri'], ENT_QUOTES), 'xoops_sitename' => $myts->makeTboxData4Show($xoopsConfig['sitename']), 'xoops_slogan' => $xoopsConfig['slogan']));


and voila, the browsertitle is multilangual.

(Phew - finally I found it

Topic | Forum


197
Daigoro
Re: How to make web-snapshot for links?

  • 2003/8/3 10:45

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


As usualy, you are right, if I search for a screen capture programs, then I will find many. But I'm looking for a browser-screen capture. One that will make a picture of the browserscreen as it's sopposed to look, and not how it's rendered in my specific screen resolusion. Also, it should be able to resize the picture.
Say I want to capture the main XOOPS site, then I would like to be able to specify that the captures file not exceed 150 pixels in width. The captureprogram should then grab the full screen in the width of the site (which appears to be something like 700 pixels), and the full height of the page (several thousand pixels). Then the picture should be scalled to 150pixels in width, and the same percentage in the height.
To do this manualy will be alot of work. Thats why I asked if anybody knew of a useable program.

Topic | Forum


198
Daigoro
How to make web-snapshot for links?

  • 2003/8/2 9:11

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


I'm wondering if anybody has made a program to make a snapshot of a site. Looking at links on various XOOPS sites, I've seen alot of snapshots - but nobody explains how they made it.
Natualy I know how to grab the full screen or window and then edit it in some kind of paint program, but what I'm looking for is a program that will automate that task.
Topic | Forum


199
Daigoro
Re: SOLVED - Making Xoops CONTENT Multilingual *Fixed Code Quote problem*

  • 2003/7/23 0:37

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


I have just hacked the tinyevent module v1.01 to be fully multilangual.

First there's a simple hack to the te_nextevents.php file located in /modules/tinyevent/blocks/

Just before the while-loop starts in line 43, I have added the following:
Quote:
$myts =& MyTextSanitizer::getInstance();


Then I replaced the following line:
Quote:
$events['event'] = $te_event['event'];

With this line:
Quote:
$events['event'] = $myts->makeTboxData4Show($te_event['event']);



Second there's also a small change to the display.inc.php file located in /modules/tinyevent/include/

I started by adding the following line as line 2, just after the php statement.
Quote:
include_once XOOPS_ROOT_PATH."/class/module.textsanitizer.php");


Then I replaced the two instanses of the following:
Quote:
printf(_TE_COMESFROM,$xoopsConfig['sitename']);


With this:
Quote:
$myts =& MyTextSanitizer::getInstance();
printf(_TE_COMESFROM,$myts->makeTboxData4Show($xoopsConfig['sitename']));


This seems to work for me.

I've noticed one tiny flaw, which I can't realy figure out.
If I have an event written in Japanese, then sometimes when I click on the 'printer frindly' icon, the encoding changes to 'Western European' instead of the 'Japanese (EUC)' I was just using on the previous page. If you have any idear why, please let me know!

I hope I remembered to mention all of the changes I made to the files to make it work.

--
Daigoro
Topic | Forum


200
Daigoro
Re: SOLVED - Making Xoops CONTENT Multilingual *Fixed Code Quote problem*

  • 2003/7/22 8:01

  • Daigoro

  • Quite a regular

  • Posts: 223

  • Since: 2003/7/3 2


Hsalazar,

I was aware of the structure, and I did change the lines for all four cases. To start with I only tried the title part, but it didn't work. Then to test, I tried the slogan-part, and it's working fine.

I still have the problem with the title part, but not the slogan part.

This is what I did:

For every instance of this line:
Quote:

$xoopsTpl->assign('xoops_pagetitle', $xoopsModule->getVar('name'));

I replaced the line with this:
Quote:

$myts =& MyTextSanitizer::getInstance();
$perro = $myts->makeTboxData4Show($xoopsModule->getVar('name'));
$xoopsTpl->assign('xoops_pagetitle', $perro);


And for every instance of this line:

Quote:

$xoopsTpl->assign('xoops_pagetitle', $xoopsConfig['slogan']);

I replaced the line with this:
Quote:

$myts =& MyTextSanitizer::getInstance();
$perro = $myts->makeTboxData4Show($xoopsConfig['slogan']);
$xoopsTpl->assign('xoops_pagetitle', $perro);


Just to make sure I'm not confusing things. The title part mentioned above means the browser title, currently reading XOOPS Official Site, and the slogan part is located just next to the title, currently reading Forum.

What did I do wrong?
Topic | Forum



TopTop
« 1 ... 17 18 19 (20) 21 »



[Advanced Search]

Login

Register now!  |  Lost Password?

Search

Advanced Search

Recent Posts

Who's Online

60 user(s) are online (49 user(s) are browsing Support Forums)

Members: 0

Guests: 60

more...

Donat-O-Meter

Stats
Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits