[dev] German extension-description text with umlauts referred to in description.xml, howto ?

2010-08-07 Thread Rony G. Flatscher
It seems that the extension-description element in a description.xml
file can refer to multiple files that each are authored in a different
language, e.g.:

  extension-description
src xlink:href=information/description_de.txt lang=de/
src xlink:href=information/description_en.txt lang=en/
  /extension-description

However, testing the German description file shows the German umlauts
with the wrong glyphs in the extension manager, which may indicate that
the codepage used by OOo to display the text is not matching the
codepage the text got created with.

What codepage should a German extension description file be authored, in
order for the package manager to dipslay the German umlauts correctly?
(Alternatively, is there a place where one could explicitly determine
which codepage got used to create that text? If so, where and how could
that be done?)

---rony



Re: [dev] German extension-description text with umlauts referred to in description.xml, howto ?

2010-08-07 Thread Ariel Constenla-Haile
Hello Rony,

On Saturday 07 August 2010, 12:21, Rony G. Flatscher wrote:
 It seems that the extension-description element in a description.xml
 file can refer to multiple files that each are authored in a different
 language, e.g.:
 
   extension-description
 src xlink:href=information/description_de.txt lang=de/
 src xlink:href=information/description_en.txt lang=en/
   /extension-description
 
 However, testing the German description file shows the German umlauts
 with the wrong glyphs in the extension manager, which may indicate that
 the codepage used by OOo to display the text is not matching the
 codepage the text got created with.
 
 What codepage should a German extension description file be authored, in
 order for the package manager to dipslay the German umlauts correctly?
 (Alternatively, is there a place where one could explicitly determine
 which codepage got used to create that text? If so, where and how could
 that be done?)
 
 ---rony

according to 
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extension_Description
The description files must contain UTF-8 encoded text.
In Linux UTF-8 is the default, so I guess you are using Win, aren't you? A 
good editor can change the encoding.

Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


signature.asc
Description: This is a digitally signed message part.