Bug 107292 - Bitstream Vera fonts are unsuitable for Czech language
Summary: Bitstream Vera fonts are unsuitable for Czech language
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: openoffice.org
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-16 16:22 UTC by Miloslav Trmac
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version: 1.1.0-3
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2003-10-27 09:19:35 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Miloslav Trmac 2003-10-16 16:22:16 UTC 
Description of problem:
The new default fonts in OpenOffice.org (Writer at least) are Bitstream Vera.
They lack some characters (at least ď, &ncaron:, ť I can dig up
the complete list) needed for Czech (locale cs_CZ{,.UTF-8}).

<whining>
This is a regression from RHL 9 and a major annoyance for people speaking Czech.
</whining>

Version-Release number of selected component (if applicable):
openoffice.org-1.1.0-2

Additional info:
This might be an issue for other European languages, at least Slovak, too.
Comment 1 Dan Williams 2003-10-16 16:38:33 UTC 
I assume that Luxi Sans would be a better option for Eastern European languages?
 I believe that's the default for OOo 1.0.2 on Red Hat.
Comment 2 Dan Williams 2003-10-16 16:39:17 UTC 
accepting
Comment 3 Miloslav Trmac 2003-10-18 14:50:59 UTC 
1.0.2 in RHL 9 actually used Nimbus Roman, but Luxi Sans is fine.
Comment 4 Dan Williams 2003-10-20 20:24:30 UTC 
If you choose Tools->Options->Accessiblity and check "Use System Font", is that
better?
Comment 5 Miloslav Trmac 2003-10-23 06:45:19 UTC 
Sorry for the delay.
That setting changes only the UI (menus...) font, it has no effect on
document fonts. The change makes the menu look more ugly though.
Comment 6 Miloslav Trmac 2003-10-27 09:19:35 UTC 
Fixed in openoffice.org-1.1.0-3. Thanks!
Note You need to log in before you can comment on or make changes to this bug.