Am Mittwoch, den 30.11.2005, 09:57 +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.
Yes: $ echo $LANG de_DE.ISO8859-1 > If you set LANG to something like > "de_DE.UTF-8" the problem should go away. I cannot do that, because I know of some system tools still having problems with utf8. The only option for me here would be to reset $LANG in the OOo startup script (I'll try that). Which does not help, the appearance of the garbled chars chagnes but they're still not correct. > 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 see. > 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. I'll write down the issue when fact are complete (and I find the time ;) and post the number here. Thank you very much, Marc --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
