Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help.
Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information.
Not enough pictures. Any additional feedback? You need to remove the font cache file and prevent it's future creation. Please close any running instances of the OpenOffice. Open a shell or a terminal. Change to the directory that contains your OpenOffice. If you made a multi user installation i. There please issue the following commands:. Then restart OpenOffice. The problem should be gone now. Close OpenOffice. If the problem is back double check the font cache file:.
The FreeType library has been compiled with auto-hinting enabled and byte-hinting disabled. While auto-hinting does a reasonable job for grid fitting it's result is still inferior to byte-hinting for many fonts.
Currently there is no workaround for this issue. It is recommended to use an XServer that supports the antialiased graphical representation of glyphs for improved readability.
Fonts are installed on the system, but they do not appear in the font list box of the OpenOffice. Fonts are installed as TrueType or Type1 fonts and are expected to be displayed antialiased but it are not, even though antialiasing is working in principle. The first legacy foundry is the XServer.
These fonts are available for displaying only. They are rasterized using the FreeType library. They are available for displaying and printing purposes. If a font is available from both foundries rastering by FreeType is preferred. The writer application offers only fonts that are available for both the display and for printing. Since fonts advertised only by the XServer are not available for printing they often do not show up in the font list box of the writer application. They will only show up if the font name matches a font that is resident in the selected printer standard fonts like Helvetica, Times, Courier are available in virtually all PostScript printer models.
To install fonts for all OpenOffice. If the fonts are installed in one of the above mentioned directories they should be available for OpenOffice. The fontpath is a comma separated list of directories that is searched for fonts by the XServer. Please note that as given in 4 OpenOffice. Therfore setting up the font for your local XServer is enough.
If you want to add fonts that are used exclusively in OpenOffice. Adding fonts with spadmin is described in the setup guide. The same is true if you want to make sure that your fonts are available on a remote display connection.
Since the fontpath is only valid on the machine the XServer is running on you are better off installing the fonts locally on your machine or on a directory that is shared between the XServer and OpenOffice. Most home user will run their XServer locally. They only need to add the fonts to the local fontpath. This file needs to have the same base name as the font file i. It must be installed in the same directory as the font file or in a subdirectory named "afm".
This file is kind of hard to read but it states all font files that have been found during the last run of OpenOffice. Even though it is safe to remove this file please be careful not to modify it. Reading or interpreting information of a font file can lead to a segmentation violation in the FreeType rasterizer. Most often this is a problem with TrueType fonts that do not strictly follow the TrueType font format specification.
Since crashes can be caused by quite many reasons it's important to explicitly identify the problem as a font problem. To do so it's useful to reset the fonts in use to the bare minimum. On a Linux box this can be achieved by restricting the fontpath with the command "xset":. It is necessary to issue the command as a single command line without having spaces between the path elements and the ",". Since OpenOffice. If the problem persists it's probably not a font problem.
The next step is to exactly identify the font that causes the crash. The rule of thumb is to enlarge the fonts in use up to the original settings. The command. The fontpath can be shown with. By consecutively removing directories from the fontpath until the problem disappears it's possible to identify the directory that contains the problematic font.
Open File Explorer and navigate to the following folder. If you see a prompt asking if you want to replace a file, allow it to be replaced. You can also delete the font from the above location , and then copy it again. Check font file Check if the font file is corrupted or not. Download and install IrfanView. Open the font file in IrfanView. If the app is able to preview the font without any errors, the file is not corrupt. If the file does not open , or it opens but some characters do not render, there is a problem with the file.
Try downloading it again, or using a different font. To check the font type, look at the extension of a font file. Get daily tips in your inbox Newsletter.
Leave a Reply Cancel reply Your email address will not be published.
0コメント