Buenos diaz Ariel, On 08.08.2010 05:46, Ariel Constenla-Haile wrote: > 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 > Thank you very much for that link (I did not find it, though I must say I did not look for an individual wiki per element) !
> "The description files must contain UTF-8 encoded text." > Again, thank you very much, that was it ! (And in hindsight, I should have thought of UTF-8 in the context of OOo!) > In Linux UTF-8 is the default, so I guess you are using Win, aren't you? A > good editor can change the encoding. > Well, both worlds, where the main one is Windows at the moment, but lately I have been busyly re-exploring installation stuff on Linux (working on a one-click installer for BSF4ooRexx which makes the ooRexx scripting language with OOo support available not only on Windows, but with the same simplicity for Linux - testing on the latest Ubuntu). One editor I like to use is vim/gvim (for which I also created the syntax highlighting for ooRexx, as the OOo snippets use vim to syntax highlight the code). --- "So oder so:" I owe you almost an entire case of beer by now, judging from all the great help (from hints, pointers to out-grown examples) you have been given on poor people's requests ! (Are you participating at the upcoming OOo-Con in Budapest by any chance?) Again, thank you very much! ---rony --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
