Hi again, the issue is filed, a workaround for *nix like OSs is found, now I have to care for Windwos...
Is there any conversion method somewhere in the API that can be hijacked from SBASIC for converting the Dictionary entries to the right encoding? Any service will do, as long as it has something like "String Utf8ToCurrentLocale(String)" and "String CurrentLocaleToUtf8(String)" to use wehn transferring. TIA, Marc Am Mittwoch, den 30.11.2005, 09:57 +0100 schrieb Stephan Bergmann: > Marc Santhoff wrote: > > Am Dienstag, den 29.11.2005, 09:56 +0100 schrieb Stephan Bergmann: [...] > Two things I noticed when trying to reproduce this: > > 1 You must be using a non-UTF-8 locale (probably 8859-1), check the > environment variable LANG. If you set LANG to something like > "de_DE.UTF-8" the problem should go away. > > 2 If you modify the Basic script by adding > > tEnd = tmpDoc.Text.getEnd() > tEnd.String = "äöü" > end sub > > to the end, you see that Basic is not the culprit, as the umlauts show > up correctly in the writer doc, regardless of LANG setting. > > I suspect that the OOo dictionary implementation erroneously uses > osl_getThreadTextEncoding() (which depends on LANG) to translate the > (obviously UTF-8 encoded) strings within the dictionary data base to > Unicode. Please update the issue (did you already write one?) accordingly. > > -Stephan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
