i18n glossary

Hello,

I would have an english glossary to help translators to catch semantic
of some expressions and help to have some coherence in expressions used.

An example: Does the document tab 'view' use the verb or the name ?

If it's the name then the document tab 'edit' should be a name too.
In the other hand, if it's a verb, 'contents', 'version', etc should be
verbs too.

Denitions would be translation oriented in that they would not defined
what does the word is but what it represent in the UI.

I hope we'll have less flames in localized list for some terms with this
tool.

Regards,
--

-- 
Encolpe Degoute
INGENIWEB (TM) - S.A.S 50000 Euros - RC B 438 725 632
17 rue Louise Michel - 92300 Levallois Perret - France
web : www.ingeniweb.com - « les Services Web Ingénieux »
Tel : 01.78.15.24.03 / Fax : 01 47 57 39 14

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: i18ndude 3.0 release?

patrimith wrote:
> Is there any reason why i18ndude 3.0 would not work on Plone 2.5 Products?
> 
> That will be what I am initially working with.

It should work just fine.

Hanno

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

Re: Major Plone translations update

Hanno Schlichting a écrit :
> Hi all,
> 
> today I updated all the translation files to match the Plone 3.0 release
> candidate 1 state.

Hello,
you also add a kupu subdirectory within two new pot files.
If you try to update with 'msgmerge -U kupupox-fr.po kupupox.pot' you
would get an error cause by \' but needed in javascript code.

What's the method to update these po files ?

Regards,

--

-- 
Encolpe Degoute
INGENIWEB (TM) - S.A.S 50000 Euros - RC B 438 725 632
17 rue Louise Michel - 92300 Levallois Perret - France
web : www.ingeniweb.com - « les Services Web Ingénieux »
Tel : 01.78.15.24.03 / Fax : 01 47 57 39 14

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Plone-i18n mailing list
Plone-i18n <at> lists.sourceforge.net

Re: i18n glossary

On Thu, 02 Aug 2007 06:51:55 -0700, Encolpe Degoute  
<encolpe.degoute <at> ingeniweb.com> wrote:

> I would have an english glossary to help translators to catch semantic
> of some expressions and help to have some coherence in expressions used.

I assume you know about  
http://plone.org/development/teams/i18n/language-specific-terms/

> An example: Does the document tab 'view' use the verb or the name ?
>
> If it's the name then the document tab 'edit' should be a name too.
> In the other hand, if it's a verb, 'contents', 'version', etc should be
> verbs too.

Use whatever feels "right" in your language. In English, it really doesn't  
make sense to enforce one or the other, but it might in French. In  
Norwegian, I have changed some of the terms to fit better with how our  
language works. Be flexible, and strive for good language, even if it  
sacrifices some precision.

--

-- 
Alexander Limi · http://limi.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________

Re: i18n glossary

Alexander Limi wrote :
> On Thu, 02 Aug 2007 06:51:55 -0700, Encolpe Degoute  
> <encolpe.degoute <at> ingeniweb.com> wrote:
> 
>> I would have an english glossary to help translators to catch semantic
>> of some expressions and help to have some coherence in expressions used.
> 
> I assume you know about  
> http://plone.org/development/teams/i18n/language-specific-terms/

We are refactoring this on another site with a more flexible format than
a Page.

>> An example: Does the document tab 'view' use the verb or the name ?
>>
>> If it's the name then the document tab 'edit' should be a name too.
>> In the other hand, if it's a verb, 'contents', 'version', etc should be
>> verbs too.
> 
> Use whatever feels "right" in your language. In English, it really doesn't  
> make sense to enforce one or the other, but it might in French. In  
> Norwegian, I have changed some of the terms to fit better with how our  
> language works. Be flexible, and strive for good language, even if it  
> sacrifices some precision.

It was easy to do we only one guy/girl translated whole plone. Now it
become very difficult to choose the good translation when ten persons
are giving their opinion. Some of them are stricter that we are when we
choose english expressions.

Re: i18n glossary

On Thu, 02 Aug 2007 13:38:48 -0700, Encolpe Degoute  
<encolpe.degoute <at> ingeniweb.com> wrote:

> It was easy to do we only one guy/girl translated whole plone. Now it
> become very difficult to choose the good translation when ten persons
> are giving their opinion. Some of them are stricter that we are when we
> choose english expressions.

Sounds like the classic French Situation™ ;)

(I really need to write that up in an article on my site sometime)

Anyway, if you choose to deal with ten people, those ten people should  
work out a policy. I don't think it's easy to generalize this in any  
meaningful way.

--

-- 
Alexander Limi · http://limi.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Plone-i18n mailing list
Plone-i18n <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Term "Also available in presentation mode"

Hi,

the term Also available in presentation mode… is translated in plone- 
de.po, but it does not show up in my testinstance.  Can anybody  
confirm this as a bug?

juh

--

-- 
www.sudelbuch.de
Satiren und Essays

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

_______________________________________________
Plone-i18n mailing list
Plone-i18n@...
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Re: Term "Also available in presentation mode"

Jan Ulrich Hasecke wrote:
> the term Also available in presentation mode… is translated in
> plone-de.po, but it does not show up in my testinstance.  Can anybody
> confirm this as a bug?

Confirmed and fixed in SVN :)

Hanno

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Plone-i18n mailing list
Plone-i18n <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n

Plone 3.0 release imminent! Complete your translations and translate the front page! :)

Hi all,

Just wanted to remind you that the last chance to get translations  
included in the 3.0 release is to have them done by Thursday.

Additionally, a lot of people don't seem to know that you can actually  
have a native-language front page now — when you create a Plone site, it  
will look at your browser language preferences, and default to your  
currently selected language — and insert a translated front page *if it  
exists*.

Here's how to create a translated front page:

1) Open PloneTranslations/locales/plonefrontpage.pot

2) Translate it, keeping the HTML tags (I know it sucks to translate HTML  
documents in po formats, but tools can help here — poEdit handles it  
pretty well)

3) Double-check that the file has the right language in the header / prefs

4) Save the translation as "plonefrontpage.po" in  
PloneTranslations/locales/≤yourlanguagecode>/

5) Check that it works by adding a new Plone site using a browser that has  
your language as the preferred language

6) svn add your file

7) svn commit :)

Re: Plone 3.0 release imminent! Complete your translations and translate the front page! :)

On Tue, 14 Aug 2007 16:48:09 -0700, Alexander Limi  
<limi <at> plone.org> wrote:

> 3) Double-check that the file has the right language in the header /  
> prefs

Actually, this isn't necessary with the LC_MESSAGES structure. :)

--

-- 
Alexander Limi · http://limi.net

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Plone-i18n mailing list
Plone-i18n <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/plone-i18n