Created attachment 49833 [details]
contains 'superscript zero'

Created attachment 49834 [details]
contains umlauts, latin characters and digits only

Sorry some corrections:

I have two files: one (bad.odt) that contains the unicode character 'superscript
zero' / U+2070 + some umlauts and another one (good.odt) with 'superscript zero'
removed. Opening bad.odt in a fresh instance of OOorg breaks the display of the
umlauts but not of other latin characters or digits. If I open good.odt first
in fresh instance of OOorg and bad.odt while good.odt is still open - everything
will be okay.

The problem can be reproduced in OOorg 2.2.1 and 2.3.0 but not in 2.0.x.

Cheers,
Torsten

For me all characters are displayed correct. I work on WinXP with German OOo.

Can you please attach a picture, which shows the "broken" display?

My Bitstream Serif font has the file VeraSe.ttf; 58.8KB; 2003-04-16. It does not
contain a glyph for U+2070. Which is your font-file? Does it contains a glyph
for U+2070?

Does the problem also occur, if you use another font for the document?

Created attachment 49836 [details]
screenshot of loaded bad.odt

Created attachment 49837 [details]
screenshot of bad.odt loaded after good.odt

Reassigned to SBA.

The problem remains after changing the font to Microsoft's Arial in both
documents. How can I search for a specific glyph in a TTF file? Is there any
tool available for Linux? My VeraSe.ttf has 60280 bytes and is from 2006-07-19.

@bollin 

1. you should really replace your Vera fonts with DejaVu (http://dejavu.sf.net),
it has filled many glyph holes in Vera, and Vera is basically unmaintained nowadays

2. The gnome tool "gucharmap" is pretty good to show you what glyph is available
for what font (select a font, go to the desired codepoint, right-click on the
glyph and it'll tell you if the glyph is available on the selected font,
substituted from another, or not available at all)

Thanks for pointing me to Dejavu and gucharmap. Dejavu really fixes the problem
for me and gucharmap is really useful. But I still consider this as a bug,
because it cannot be reproduced in OOorg 2.0 or in the Windows version.

Unable to reproduce using OOo2.3.1B9238 (Sun) Linux i86 RPM de_DE under openSUSE
10.2.

I can reproduce it with version 2.4.0-5 on Debian.

mbayer->bollin: Please adhere to our issue description guidelines.

mbayer->bollin: Please clarify whether you are using the “vanilla†OOo (i.e.
downloaded from openoffice.org) or a distribution build (e.g. Debian, openSUSE).
The version number you indicate in desc13 sounds somewhat strange.

It is the distribution build which is currently in Debian/testing.

Closing as WFM due to comments in desc16.

mbayer->bollin: Please report issues in distribution builds to the respective
distributor. In case you encounter again problems with OOo, please double-check
you are using the “vanilla†OOo (i.e. the stable build from our site).

I can easily reproduce it with OOo_2.4.1_LinuxIntel_install_en-US.tar.gz .

I forgot to mention that the problem vanishes after removing the 'Bitstream
Vera' fonts from my systems. I think it is still a bug.

The error can be reproduced on a freshly installed Ubuntu 8.04 with both the
distribution and the upstream build of OOorg. The package ttf-bitstream-vera is
installed by default in Ubuntu.

Same root cause as issue 88376

*** This issue has been marked as a duplicate of 88376 ***

SBA: Closing duplicate.
Note that issue 88376 is fixed and verified for OOo 3.0 (integrated since Build
OOO300_m4).