Sorry! The attached file is automatically replaced by

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

so I could not see the difference ! Anyway, I am not familiar with the technique that you mention.
Marc H.


Zhenwu Duan a Ãcrit :

hello marc,
i don't mean to use writer to write german characters (ÃÃÃÃ), that's ok for me too.
but if you create a self-made oo-file (foo.sxw), use java or other programming language,
open this foo.sxw, oo-wirter will be automatically called, the german character in this file is then unreadable.
i attached two files which show the difference. one is writerGenerated.sxw, which displays all german very fine,
another is selfGenerated.sxw, in which german is unreadabel.
WertzuÃÃÃ-Ã#+*?=)((/%$%$ÃÃÃÃÃÃÃ----asdfgh
WertzuÃÃÃ-Ã#+*?=)((/%$%$ÃÃÃÃÃÃÃ----asdfgh
hier you see, the lower case characters like ÃÃÃ are ok, but ÃÃÃ are changed as ÃÃÃ. this is my problem.


thank anyway for respons!


-----UrsprÃngliche Nachricht----- Von: Elsasser [mailto:[EMAIL PROTECTED] Gesendet: Dienstag, 26. April 2005 15:01 An: [email protected] Betreff: Re: [users] german Umlaut in Uppercase, a bug or fonts problem?


That is strange : I never had any problem with German characters. Maybe you have special options on your computer that make OO ok for other languages, but not for West European languages. Here these characters extracted from the OO-writer screen


ÃÃÃÃÃÃÃ

Did you verify your "Language" option ? Do you have any problems with

ÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃÃ ?
I saved the concerned file and then opened it, and got the characters correctly.
Marc H.




Zhenwu Duan a Ãcrit :



Hello,

can anyone please give me some help to my problem by creating a document (foo.sxw) for openoffice-writer.
a self created content.xml with german charactors like: Ã Ã Ã Ã Ã Ã Ã
our problem is, it is ok for à à à (low case), but not for à à à Ã, after opening the fle foo.sxw we got the charators (upper case and Ã) unreadable.


we tried with release 1.1.1, 1.1.4 and the newest 2.0(1.9.7)
the problem stays the same.

I replaced encoding="UTF-8" with ending="ISO-8859-1", but
it did not help.

Is it really a known bug? is there already a solution?


thanks.




------------------------------------------------------------------------

---------------------------------------------------------------------
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]



Reply via email to