Apache OpenOffice (AOO) Bugzilla – Issue 22367
Patch for debbuging problems on fontnames
Last modified: 2004-02-05 10:36:31 UTC
This patch will help you look into problems caused by font name mismatch on UNIX machines, such as "Mojibake" in Japanese for garbage characters in English. Once apply this patch, your OOo will produce diagnosis messages on your console reporting what font names and texts are being involved. To apply this patch, simply do the following: cd $SRC_ROOT/vcl/source/gdi patch < debugging_fontnames-1.0.patch.txt cd $SRC_ROOT/vcl rm -r xxxxxxxx.pro build debug=true add_cflagscxx=-DHDU_DEBUG cp -p lib/libvcl645*.so _OOo-install-dir_/program Notes: Make sure the $LANG environment variable is set appropriately before starting the OOo, otherwise non-English fontnames or texts are not displayed correctly in the console. This patch is based on the codes tagged with a tag name in cvs: CWS_SRX645_OOO111FIX1_ANCHOR Most parts of this feature have been brought by the members of gsl, especially HDU. Tora
Created attachment 11180 [details] Patch rev. 1.0
cp->hdu: i do not understand in what way this is particularly useful nor do I understand what defining HDU_DEBUG might change. please have a look at it if you want to have it.
Patch applied to CWS vcl16 for target OOo2. HDU->CP: it just adds debugging output for GetDefaultFont(), which is getting more interesting as OOo is ported to many more languages and distributions.
.
Additional small enhancement for investigation into fontname issues. Here are two patches whose effects are same. For OOo 1.1 or 1.1.1 Patch: debugging_fontnames-1.1-for-OpenOffice_1_1.patch.txt cd $SRC_ROOT/vcl build.pl debug=true add_cflagscxx=-DHDU_DEBUG * This patch includes the changes in the previous patch debugging_fontnames-1.0.patch.txt For SRC680_m14s1 Patch: debugging_fontnames-2.0-for-SRC680_m14s1.patch.txt cd $SRC_ROOT/vcl build debug=true envcflagscxx=-DHDU_DEBUG * This patch does NOT include the changes in the previous patch debugging_fontnames-1.0.patch.txt Tora
Created attachment 11321 [details] Patch rev. 1.1 for OOo 1.1/1.1.1
Created attachment 11322 [details] Patch rev. 2.0 for SRC680_m14s1
The topmost patch got into CWS vcl16. The other patches didn't make it. If you think they are very important please open a followup issue.
I think all of these patches are important on the only special occasion where the function of finding and fallbacking fontnames is suspiciously working. In daily your development process, these patches might interfere with your tasks by a plenty of diagnosis messages that don't have any specific meanings. The main purpose of my uploading these patches was to allow Asian OOo users to solve by themselves: (1) garbage characters by setting font replace in the Tools > Options (2) collecting information on what fonts are used in a variety of platforms and proposing default font name lists in share/registry/data/org/openoffice/VCL.xcu They can build libvclxxxxx.so by themselves on demand applying these patches even if these patches are not included in the main source codes. ja.openoffice.org has planned to deliver libvcl645li.so that incorporates these patches to OOo 1.1/1.1.1 users. Please feel free to revise your source codes as you want. For example, rename the macro name in the following line. #if OSL_DEBUG_LEVEL > 1 with #if FOO_BAR > 1
Ok. To clarify my previous comment: the other patches didn't make it because the CWS where the first patch got applied was already "hands off for development". So I couldn't put them into that CWS because of time constraints, not for other reasons.
Thank you for your clarification. Now I understand.
CWS vcl16 is integrated. Closing.