From: Moritoshi O. <m-o...@10...> - 2006-06-19 00:31:19
|
> > My apology for not being able to point to the appropriate lines in a > > source file. If you could tell me exactly where those are in the > > source code, it would be very much appreciated. I really wanna learn > > egw and php. > > > I think there's no real need to dive into the php code, but lang() calls, as I > explained in my reply yesterday. Maybe if a "Japanese exclusive" date format > existed, then show it like that in the GUI (with the rest of d/m/y, etc > formats), but that would lead to "hardcode" the format, which is not > desirable. > > Please study the lang calls examples I gave yesterday, in whose case I could > even fix that myself. > Thanks for your advice. > > > Also, in Calender where you input a new plan in a small browser window: > > > > Owner [userid] Lastname FirstName Updated by > > ^^^^^^^^^^two tokens. > > > > They must be in one token for me to set a translated string in Japanese. > > > At this time, and surely due to variable font size, I can't see exactly what > you mean (though I think I get the intention). Please provide one or two real > examples of how it should (and shouldn't) be, to see if it can be fixed in the > lang() call. > Again, thanks for your advice. I will learn to use lang() calls, then hopefully, correct the situation. > > > > > 3) Strings too long(there is a max number?) or perhaps strings with > > > > some special chars(c:\) can not be displayed in the translation > > > > tool and in an application even if they are written in > > > > phpgw_??.lang file. > > > > > > I havn't met such problems(or havn't noticed...^^||). Could you > > > provide some exact information? > > > > > > > in admin lang file: > > http://host/egroupware/index.php?menuaction=developer_tools.uilangfile.edit&app_name=admin > > > > Enter the full path for temporary files.<br>Examples: /tmp, C:\TEMP > > > > Enter the full path for users and group files.<br>Examples: /files, E:\FILES > > > > These two lines can not be shown in the translation tool, but they are acutally saved in > > the phpgw_ja.lang file. > > > I can't reproduce that (I see it all in TT). I've tried my installation (with > both spanish and japanese) and no problem at all. I guess it's something > related to your installation, so try to replicate the problem in my > installation. It was not an installation issue. The problem was the TT not being able to display "<br>例:" correctly: I added a space between "<br>" and "例" in "add a new translation". How to reproduce: charset: Both in EUC-JP and UTF8 1. In Step 1 Source file: English Translation file: Japanese 2. Enter the string with "<br>例:" 3. Do the rest of steps Result: It seems that a "<br>" and the char are next to each other, it gets jammed(called "moji-bake" in Japanese). The English string/Japanese Translation string pair in the TT page was not displayed. Instead, The English string/empty pair is displayed, and additional empty/translation pair as well. Expected Result: Show the English string/Japanese Translation string pair. Workaround: Add a space between "<br>" and the next char, then follow the steps in TT. > > > I think there are other lines with the same problem in a different > > app, but I can not search more today. Please allow me to report, if > > any, later. > > > Try to reproduce everything in my installation before reporting. Maybe it's > just that utf-8 is needed and you haven't set it properly. It happens in utf-8 as well, as described above. Best regards. Moritoshi Oshiro |