Apache OpenOffice (AOO) Bugzilla – Issue 15238
integrate Bitstream Vera Fonts
Last modified: 2004-02-15 07:30:42 UTC
integrated.
verified.
One patch is still missing - Kevin, please, attach it so other buildiers could take it and test it before integration. The problem is that those fonts are not copied into fonts/truetype directory.
Created attachment 6857 [details] patch to deliver Bitstream Vera Fonts for scp
Hi, One other change I think we need until the Bitstream Vera fonts support more of the other latin based encodings (iso-8859-2 and etc) is to make sure that Luxi Sans is found as a UI font before any Bitstream Vera Sans font is found since Luxi fonts are part of XFree86 4.3.0 and even include Windows encodings cp-1252 and iso-8859-X where X is 1,2,3,4,9,13,15. So that means slight updates to: vcl/source/gdi/outdev3.cxx vcl/source/gdi/fontcfg.cxx officecfg/regsitry/data/org/openoffice/VCL.xcu So that for all UI purposes Luxi Sans can be found first before Bitstream Vera Sans so that setup.bin and the menus will work in iso-8859-1,2,3,4,9.13,and 15 lands. I am putting together patches to do this right now on my own box and attach them here after testing. Kevin
Kevin, what is the status? I think that scp patch could be applied now so other localizators could test the effect of integrating Bitstream fonts. What do you think?
Hi Pavel, They have applied in someplace else in scp (see setupzip.scp) so we should be okay with this one and it shoudl be closed as fixed I think. Kevin
Yes, it is in setupzip.zip. Thanks. The problem with using Bitstream Vera remains - do you have something for testing? BTW - when Luxi is to be found before Bitstream Vera, does this mean that Bitstream Vera will be useless for UI purposes?
Hi, I think we will need to add Luxi in from of all of the Bittream Vera fonts so that iso-8859-2 and others will work. The problem is then Bitstream Vera will not be used in iso-8859-1 and etc. So perhaps for the time being we can ifdef this for iso-8859-2 locales. Until we add glyphs to the Vera, I see no other viable solution. Kevin
You shouldn't try to handle them all under the "en" language setting in VCL.xcu. You should specify Vera for Latin-1 languages and Luxi for Latin-2 languages but each language needs an entry in VCL.xcu.
mh->kevin: will you do the "luxi" patch ?
Hi Pavel, Can you check if the following patch to officefg/registry/data/org/openoffice/ to VCL.xcu under cs_CZ will work for you. If so we can do the same for sk_SK and pl_PL. --- VCL.xcu.~1.17.~ 2003-06-12 07:06:48.000000000 -0400 +++ VCL.xcu 2003-06-30 11:33:57.000000000 -0400 @@ -137,6 +137,77 @@ <value>Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma;Bitstream Vera Sans;Interface User;WarpSans;Geneva;Tahoma;MS Sans Serif;Helv;Dialog;Albany;Lucida;Helvetica;Charcoal;Chicago;Arial;Helmet;Interface System;Sans Serif</value> </prop> </node> + + + <node oor:name="cs-CZ" oor:op="replace"> + <prop oor:name="LATIN_DISPLAY" oor:type="xs:string" oor:op="replace"> + <value>Albany;Arial;Luxi Serif;Helvetica;Lucida;Geneva;Helmet;SansSerif;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="CJK_DISPLAY" oor:type="xs:string" oor:op="replace"> + <value>Andale Sans UI;MS Gothic;HG Gothic J;HG Gothic B;HG Gothic;Gothic;MS PGothic;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="LATIN_HEADING" oor:type="xs:string" oor:op="replace"> + <value>Albany;Arial;Luxi Sans;Helvetica;Lucida;Geneva;Helmet;SansSerif;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="LATIN_FIXED" oor:type="xs:string" oor:op="replace"> + <value>Cumberland;Courier New;Luxi Mono;Courier;Lucida Sans Typewriter;Lucida Typewriter;Monaco;Monospaced</value> + </prop> + <prop oor:name="LATIN_PRESENTATION" oor:type="xs:string" oor:op="replace"> + <value>Thorndale;Times New Roman;Luxi Serif;Times;Lucida Serif;Lucida Bright;Timmons;New York;Serif</value> + </prop> + <prop oor:name="LATIN_SPREADSHEET" oor:type="xs:string" oor:op="replace"> + <value>Albany;Arial;Luxi Sans;Helvetica;Lucida;Geneva;Helmet;SansSerif;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="LATIN_TEXT" oor:type="xs:string" oor:op="replace"> + <value>Thorndale;Times New Roman;Luxi Serif;Times;Lucida Serif;Lucida Bright;Timmons;New York;Serif</value> + </prop> + <prop oor:name="CJK_HEADING" oor:type="xs:string" oor:op="replace"> + <value>HG Mincho Light J;MS Mincho;HG Mincho J;HG Mincho L;HG Mincho;Mincho;MS PMincho;HG Mincho Light J;MS Gothic;HG Gothic J;HG Gothic B;HG Gothic;Gothic;MS PGothic;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="CJK_PRESENTATION" oor:type="xs:string" oor:op="replace"> + <value>HG Mincho Light J;MS Gothic;HG Gothic J;HG Gothic B;HG Gothic;Gothic;MS PGothic;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="CJK_SPREADSHEET" oor:type="xs:string" oor:op="replace"> + <value>Andale Sans UI;MS Gothic;HG Gothic J;HG Gothic B;HG Gothic;Gothic;MS PGothic;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="CTL_DISPLAY" oor:type="xs:string" oor:op="replace"> + <value>Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value> + </prop> + <prop oor:name="CTL_HEADING" oor:type="xs:string" oor:op="replace"> + <value>Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value> + </prop> + <prop oor:name="CTL_PRESENTATION" oor:type="xs:string" oor:op="replace"> + <value>Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value> + </prop> + <prop oor:name="CTL_SPREADSHEET" oor:type="xs:string" oor:op="replace"> + <value>Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value> + </prop> + <prop oor:name="CTL_TEXT" oor:type="xs:string" oor:op="replace"> + <value>Tahoma;Lucidasans;Lucida Sans;Arial Unicode MS</value> + </prop> + <prop oor:name="SANS" oor:type="xs:string" oor:op="replace"> + <value>Albany;Arial;Luxi Sans;Helvetica;Lucida;Geneva;Helmet;SansSerif;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma</value> + </prop> + <prop oor:name="SANS_UNICODE" oor:type="xs:string" oor:op="replace"> + <value>Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma;Albany;Arial;Helvetica;Lucida;Geneva;Helmet;SansSerif</value> + </prop> + <prop oor:name="SERIF" oor:type="xs:string" oor:op="replace"> + <value>Thorndale;Times New Roman;Luxi Serif;Times;Lucida Serif;Lucida Bright;Timmons;New York;Serif</value> + </prop> + <prop oor:name="SYMBOL" oor:type="xs:string" oor:op="replace"> + <value>StarSymbol;OpenSymbol;Andale Sans UI;Arial Unicode MS;StarBats;Zapf Dingbats;WingDings;Symbol</value> + </prop> + <prop oor:name="UI_FIXED" oor:type="xs:string" oor:op="replace"> + <value>Cumberland;Courier New;Luxi Mono;Courier;Lucida Sans Typewriter;Lucida Typewriter;Monaco;Monospaced</value> + </prop> + <prop oor:name="FIXED" oor:type="xs:string" oor:op="replace"> + <value>Cumberland;Courier New;Luxi Mono;Courier;Lucida Sans Typewriter;Lucida Typewriter;Monaco;Monospaced</value> + </prop> + <prop oor:name="UI_SANS" oor:type="xs:string" oor:op="replace"> + <value>Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Tahoma;Luxi Sans;Interface User;WarpSans;Geneva;Tahoma;MS Sans Serif;Helv;Dialog;Albany;Lucida;Helvetica;Charcoal;Chicago;Arial;Helmet;Interface System;Sans Serif</value> + </prop> + </node> + <node oor:name="ar" oor:op="replace"> <prop oor:name="UI_SANS" oor:op="replace" oor:type="xs:string"> <value>Tahoma;Traditional Arabic;Simplified Arabic;Lucidasans;Lucida Sans;Supplement;Andale Sans UI;Arial Unicode MS;Lucida Sans Unicode;Interface User;WarpSans;Geneva;MS Sans Serif;Helv;Dialog;Albany;Lucida;Helvetica;Charcoal;Chicago;Arial;Helmet;Interface System;Sans Serif</value> I will add this patch to cs_CK_test.patch as attachment. Kevin
Created attachment 7273 [details] patch to test possible fix for Luxi for Vera swap
Hi Kevin, you don't need to provide the complete list of entries but you can leave out entries that are duplicate to the English settings. English is the default language and used to fill the gaps. So in order to keep the list short and readable you may want to remove at least the CTL and CJK settings (I haven't had a precise look at the patch due to a lack of time) sorry for the late reply, best regards Christof
Created attachment 7280 [details] patch to replace cs_CZ_test.patch with added support for pl_PL and sk_SK
Hi, Based on another e-mail I think the list should be at least: Czech cs-CZ Croation hr-HR Hungarian hu-HU Polish pl-PL Slovak sk-SK Slovenian sl-SL Since dictionaries exist for these locales as well. I am unsure of Bosnian, Romanian, Serbian and I saw something called Sorbian as well on an iso-8859-2 site. Is there some easy way to make one xml entry to represent this entire group of locales or do I need to have an entry for each of these? Thanks, Kevin
Okay I have now committed an extended version of this patch to support Croatian, Czech, Hungarian, Polish, Romanian, Slovak, and Slovenian That still leaves Bosnian, Serbian, and Sorbian that someone might want to add but since there were no writing aids in these locales, I was not sure of the support for them in OOo. I have also added Luxi Sans in the vcl/source/gdi/fontcfg.cxx and vcl/source/gdi/outdev3.cxx right before Bitstream Vera Sans so that the installation should be readable as well. I am now closing Issue 15238. Kevin
Kevin, setup on my system does not use Luxi - see http://www.janik.cz/tmp/snapshot003.png (it is the same as before the patch) All applications use it though - see http://www.janik.cz/tmp/snapshot004.png
Hi Paveol, I looked at the jepgs but I could not see anything obviously wrong. In vcl/source/gdi/fontcfg.cxx and vcl/source/gdi/outdev3.cxx you should see Luxi Sans before Bitstream Vera Sans in the list? Is it there? If so and if you are not seeing Luxi at setup, then you must be using some other font in that list found before the Luxi Sans? Kevin
Yes, it is Andale Mono, after removing it from fontpath, I see Luxi. So it is OK :-) Thank you.
verfied in 1.1.0.
close issue