Notes for translators

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-18-2005 04:37 AM
Use of single quote characters in messages
If the message contains a variable e.g. {0} then single quotes must be doubled up to escape them correctly e.g. convert: don't to: don''t
If the message does not contain a variable then a single quote character should be used.
If the message contains a variable e.g. {0} then single quotes must be doubled up to escape them correctly e.g. convert: don't to: don''t
If the message does not contain a variable then a single quote character should be used.
Labels:
- Labels:
-
Archive
4 REPLIES 4

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-22-2006 06:04 AM
Hi All,
Question about xlz and diff files : they are included in the english default language pack. I think they are only intended for translaters, so there is no need to include them in translated language packs.
Can you confirm ?
Laurent.
Question about xlz and diff files : they are included in the english default language pack. I think they are only intended for translaters, so there is no need to include them in translated language packs.
Can you confirm ?
Laurent.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-17-2006 06:53 AM
Hi Kevin,
I was making a quick fix to all french files where single quotes were left, and i discovered that sometimes two single quotes are used around {} variables, sometimes a double quote is used.
For example :
action-config_en_US.properties:export.store.package.description=Alfresco Repository export of store ''{0}''.
webclient.properties:delete_rule_confirm=Are you sure you want to delete \"{0}\"?
Are the two options usable, or should we only use backslashed double quotes ?
Another example : when doing a full export with alfresco, the generated content names contain {0} (cf action-config.properties:export.package.description)
Beware : attesoro does not display \", but displays " instead. I've sent a bug report to attesoro's developper. Putting a backslash in sentences using a backslash transforms it in double backslash => backslash-escaped characters are not translatable.
So, we must manually modify all attesoro translated files with a text editor to build a correct language pack.
Laurent.
I was making a quick fix to all french files where single quotes were left, and i discovered that sometimes two single quotes are used around {} variables, sometimes a double quote is used.
For example :
action-config_en_US.properties:export.store.package.description=Alfresco Repository export of store ''{0}''.
webclient.properties:delete_rule_confirm=Are you sure you want to delete \"{0}\"?
Are the two options usable, or should we only use backslashed double quotes ?
Another example : when doing a full export with alfresco, the generated content names contain {0} (cf action-config.properties:export.package.description)
Beware : attesoro does not display \", but displays " instead. I've sent a bug report to attesoro's developper. Putting a backslash in sentences using a backslash transforms it in double backslash => backslash-escaped characters are not translatable.
So, we must manually modify all attesoro translated files with a text editor to build a correct language pack.
Laurent.
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-24-2007 01:18 PM
Hello,
There are some bugs in the 2.1 version because some people have translated the Java message format patterns {0, choice, xxxx} to their own language, like {0, choisir, xxx} in French!
Be carefull, {} wrap some java instructions that must not be translated (for instance "date", "number" or "choice" should remain unchanged).
There are some bugs in the 2.1 version because some people have translated the Java message format patterns {0, choice, xxxx} to their own language, like {0, choisir, xxx} in French!
Be carefull, {} wrap some java instructions that must not be translated (for instance "date", "number" or "choice" should remain unchanged).

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2007 06:29 AM
Hello,
There are some bugs in the 2.1 version because some people have translated the Java message format patterns {0, choice, xxxx} to their own language, like {0, choisir, xxx} in French!
Be carefull, {} wrap some java instructions that must not be translated (for instance "date", "number" or "choice" should remain unchanged).
Hi, please post it in the french translation topic, otherwise i think it won't be fixed.
Laurent.
