Santiago Gala wrote:
David Sean Taylor wrote:
(...)
Japanese Jetspeed project would like to contribute to Jetspeed from
the point of view of I18n and L10n.
What other internationalization issues are you experiencing?
AFAIK, Jetspeed has little to no I18n problems. We are routinely using
UTF-8 in all our portals with no problems. I'm also curious if you have
found some extra problem.
The known/investigating issues are:
1) The .xreg and psml files is not handled by the correct encoding.
The file read issue is fixed by my proposed patches. (The .xreg file
has been fixed and psml is #13286.) But .xreg and psml files are always
stored by UTF-8, not the original encoding. The same original encoding
should be used in the read/save process.
2) The file name in TurbineUploadService has the same issue as
DefaultParameterParser. (investigating now...)
If so, I will create JetspeedUploadService...
3) The notification mail does not support character sets other than iso-8859-1.
(investigating now...)
Does Jetspeed support it for other language?
4) The portlet-entry element in portlet.xreg supports one locale only.
For example, if Japanese message is used as the title and description element
in the portlet-entry element, this message is useless for a user which does not
use Japanese. So, I think that the title and description element needs to have
such a lang attribute.
5) HTML Portlet supports one locale only.
If LoggedInWelcome.html in the LoggedInWelcome Portlet of Jetspeed is translated
in Japanese, users other than Japanese cannot understand the content of this portlet.
It is better to have a feature for dispatching files for each locale, such as
LoggedInWelcome_ja.html.
L10N to japanese is definitely another issue. It would be great to have
messages and templates (and sample PSML resources) for Japanese.
The approach of the message properties files and templates is important for L10n work.
But I think that it is better that all messages in the default template files are picked up
to the message properties file. If not so, the L10n developer/translator has to change the
same template file as the changed default file. It is difficult for them to have to change it
by the simple layout changes, not the message changes. I think that the L10n member(including
me) cannot track _all_ template files. For templates, I'd like to use it for fixing the layout
issue of L10n. For instance, in Japanese env., since the name order is "LastName FirstName",
only templates including the name info need to be created for Japanese.
So, it is not easy to localize Jetspeed if all messages are not picked up to the properties file.
(In Japanese L10n Jetspeed project, all messages in velocity templates are picked up to
the message properties file.)
Best regards,
shinsuke
__________________________________________________
Do You Yahoo!?
Yahoo! BB is Broadband by Yahoo! http://bb.yahoo.co.jp/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
