[jbosstools-dev] Suggested coding guidelines for internationalisation

[Sean Flanigan]

Denis, Snjezana, John,

Thanks for the info about plugin.properties and $plugin/nl, that's
useful to know, at least for me.  If we need to, we can put $plugin/nl
into fragments, and thus include images in langpacks.

I'm not sure if you want any of that in the coding guidelines, but if
so, I've started a wiki page for the draft version here:

http://www.jboss.org/community/docs/DOC-12852

Sean.

Denis Golovin wrote:
> Or they are placed under plugin.name/nl in language folder i.e.
> 
> plugin.name/nl/de
> plugin.name/nl/ru
> etc.
> 
> they can also contain images (icons, splash screens) and can be 
> referenced in plugin.xml with $nl$ prefix in path i.e. $nl$/splash.bmp
> 
> some information about it is here 
> http://help.eclipse.org/ganymede/topic/org.eclipse.platform.doc.isv/guide/product_def_nl.htm
> 
> Denis
> 
> Snjezana Peco wrote:
>> There is a specific kind of properties files in Eclipse that are used 
>> for internationalizing plugins and features, i.e., plugin.xml, 
>> feature.xml and MANIFEST.MF. They are usually named plugin.properties 
>> and feature.properties and placed in the root of a plugin/feature (out 
>> of the source directory).
>>
>> Snjeza

-- 
Sean Flanigan

Senior Software Engineer
Engineering - Internationalisation
Red Hat

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 551 bytes
Desc: OpenPGP digital signature
Url : http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20081024/91630c3b/attachment.bin