[WG: I18N & L10N] [Building Sakai] how to set ? (i18n best practice included)

Tue Sep 4 04:15:06 PDT 2012

Date formats like those in.the jar tools may not need translation but they do need localization.

Sent from my HTC

----- Reply message -----
From: "Steve Swinsburg" <steve.swinsburg at gmail.com>
To: "Jean-Francois Leveque" <jean-francois.leveque at upmc.fr>, "Bryan Holladay" <holladay at longsight.com>
Cc: "i18n at collab.sakaiproject.org" <i18n at collab.sakaiproject.org>, <sakai-dev at collab.sakaiproject.org>
Subject: [Building Sakai] [WG: I18N & L10N] how to set ? (i18n best practice included)
Date: Tue, Sep 4, 2012 12:58 pm
Agreed, this makes it difficult to translate accurately.
Bryan, there is a separate properties file loader in the Sakai Wicket Maven Archetype that uses commons-configuration to load in SQL properties (could be any arbitrary property though), might be useful here.

cheers,Steve

On Tue, Sep 4, 2012 at 6:34 PM, Jean-Francois Leveque <jean-francois.leveque at upmc.fr> wrote:

I think the key that have values that should be translated should be in

a different file than the ones that have values that should not be

translated.

Using ResourceLoader to load values that should not be translated is

dangerous because it renders the debug locale (en_US_DEBUG) useless. It

also creates a risk of a local (or submitted) translation breaking Sakai.

Comments in the file are not enough, AFAICT.

Please create i18n files that can completely be translated and use

ResourceLoader and create separate files for values that should not be

translated and do not use ResourceLoader to load these values.

ResourceLoader is tailor-made for Sakai i18n and it shouldn't be used

for anything that is not i18n.

Thanks

J-F

On 01/08/2012 18:11, Bryan Holladay wrote:

> The issue is that the translation translated more than it should have.

>   The tutorial tool uses the properties file differently than most

> tools in order to easily add new pages without having to make any code

> changes.  There are only two places where you should translate:

> anything that ends with ".title" or ".body".  The rest are used by the

> tool to know where to show the page, what to point to and what is the

> next/previous page.  The mongolian translation translated too much.

> Matt J has created a ticket

> https://jira.sakaiproject.org/browse/SAK-22443 for this issue.  I

> should have put comments in the properties file about this.

>

> Thanks

> Bryan

>

> On Wed, Aug 1, 2012 at 2:11 AM, Matthew Jones<matthew at longsight.com>  wrote:

>> The tutorial is a new feature for 2.9 and we plan to disable it for the

>> regular release because it won't be translated to all languages in time for

>> 2.9.0. What you're seeing is probably a bug in general with the tutorial

>> entity not correctly picking up the language set in the session (or even

>> possibly on the server)

>>

>> You can disable it with the property

>> portal.use.tutorial=false

>>

>> We'd have to look at why it's not working.

>> https://source.sakaiproject.org/svn//help/trunk/help-component/src/java/org/sakaiproject/component/app/help/TutorialEntityProviderImpl.java

>>

>> Someone's already submitted translated files, but I'd doubt it was actually

>> tested with any language other than English.

>>

>> As far as the footer, that is a property that by default is this:

>>

>> #bottomnav.count = 3

>> #bottomnav.1 =<a href="/portal/site/!gateway">Gateway</a>

>> #bottomnav.2 =<a href="/portal/pda">Mobile View</a>

>> #bottomnav.3 =<a href="http://www.sakaiproject.org/" target="_blank">The

>> Sakai Project</a>

>>

>> On Tue, Jul 31, 2012 at 11:23 PM, Baynaa_sk<baynaa.sk at gmail.com>  wrote:

>>>

>>>

>>> Whenever new user registers to the system and the system automatically

>>> logs

>>> in the new user, all the tools are displayed in English.

>>>

>>> When new user logs in, the system shows tutorial page in English. Where

>>> can

>>> I find these tutorial files so that I can translated them to Mongolian?

>>>

>>> Is it possible to modify Sakai footer? for example, I would like add

>>> little

>>> different description to the footer.

_______________________________________________

i18n mailing list

i18n at collab.sakaiproject.org

http://collab.sakaiproject.org/mailman/listinfo/i18n

TO UNSUBSCRIBE: send email to i18n-unsubscribe at collab.sakaiproject.org with a subject of "unsubscribe"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/i18n/attachments/20120904/5400cf1e/attachment-0001.html 