Created attachment 32750 [details]
The patchpack

Created attachment 32751 [details]
Packed DejaVu fonts ver. 2.1

Homepage of the DejaVu font: http://dejavu.sourceforge.net/
License: Fonts are © Bitstream (same as Bitsteram Vera). DejaVu changes are in
public domain. 

Bitsream Vera supports only Latin1 characters. DejaVu supports a lot more, see
at:http://dejavu.sourceforge.net/wiki/index.php/Current_status

DEFECT->ENHANCEMENT

Interesting, I've just been adding dejavu fonts to ooo-build

Did you updated the help's stylesheets?

ssa->hdu: when evaluating this patch please check with mh possible licensing issues

I will incluide a non tested patch that replaces all bitstream related infos to
dejavu and neutral fonts. Please review it.

Created attachment 33284 [details]
Full patchset to remove Bitstream and add DejaVu with neutral "fonts" prj, dir

Created attachment 33385 [details]
Updated DejaVu fonts 2.2, corrected patches...

.

I think this is for 3.0...

For the correct solution we have to set font replacement like this (file:
OpenOffice.org2/user/registry/data/orgo/penoffice/Office/Common.xcu):

 <node oor:name="Font">
  <node oor:name="Substitution">
   <prop oor:name="Replacement" oor:type="xs:boolean">
    <value>true</value>
   </prop>
   <node oor:name="FontPairs">
    <node oor:name="_0" oor:op="replace">
     <prop oor:name="Always" oor:type="xs:boolean">
      <value>false</value>
     </prop>
     <prop oor:name="OnScreenOnly" oor:type="xs:boolean">
      <value>false</value>
     </prop>
     <prop oor:name="ReplaceFont" oor:type="xs:string">
      <value>Bitstream Vera Sans</value>
     </prop>
     <prop oor:name="SubstituteFont" oor:type="xs:string">
      <value>DejaVu Sans</value>
     </prop>
    </node>
    <node oor:name="_1" oor:op="replace">
     <prop oor:name="Always" oor:type="xs:boolean">
      <value>false</value>
     </prop>
     <prop oor:name="OnScreenOnly" oor:type="xs:boolean">
      <value>false</value>
     </prop>
     <prop oor:name="ReplaceFont" oor:type="xs:string">
      <value>Bitstream Vera Sans Mono</value>
     </prop>
     <prop oor:name="SubstituteFont" oor:type="xs:string">
      <value>DejaVu Sans Mono</value>
     </prop>
    </node>
    <node oor:name="_2" oor:op="replace">
     <prop oor:name="Always" oor:type="xs:boolean">
      <value>false</value>
     </prop>
     <prop oor:name="OnScreenOnly" oor:type="xs:boolean">
      <value>false</value>
     </prop>
     <prop oor:name="ReplaceFont" oor:type="xs:string">
      <value>Bitstream Vera Serif</value>
     </prop>
     <prop oor:name="SubstituteFont" oor:type="xs:string">
      <value>DejaVu Serif</value>
     </prop>
    </node>
   </node>
  </node>
 </node>

It replaces the font when Bitstream Vera is not available...
In my opinion we can do it for 2.0.3 with carefully testing... For example I
will upload a build soon for testing...

Windows builds with DejaVu fonts:
http://ftp.fsf.hu/OpenOffice.org_hu/devel/M150_Premium/

Font replacement is not set...

set target to 2.0.3

I suggest not to replace Bitstream Vera to DejaVu everywhere, just put DejaVu
before Bitstream Vera in the lists. Not everybody packages OOo with fonts and we
cannot expect that DejaVu is present on all target systems (e.g. on Linux
distributions). Bitstream Vera is more widespread. 

For example in vcl/source/gdi/fontcfg.cxx I would write:
#define FALLBACKFONT_UI_SANS "Andale Sans UI;Tahoma;Arial Unicode
MS;Arial;DejaVu Sans;Bitstream Vera Sans;gnu-unifont;Interface
User;Geneva;WarpSans;Dialog;Swiss;Lucida;Helvetica;Charcoal;Chicago;MS Sans
Serif;Helv;Times;Times New Roman;Interface System"
#define FALLBACKFONT_UI_SANS_LATIN2 "Andale Sans UI;Tahoma;Arial Unicode
MS;Arial;DejaVu Sans;Luxi Sans;Bitstream Vera Sans;Interface
User;Geneva;WarpSans;Dialog;Swiss;Lucida;Helvetica;Charcoal;Chicago;MS Sans
Serif;Helv;Times;Times New Roman;Interface System" 

Please note that in the LATIN2 line I put DejaVu before Luxi, because DejaVu
looks nicer than Luxi and we would like to use it, if it is available.

The same applies to officecfg/registry/data/org/openoffice/VCL.xcu and
helpcontent css files (dejavufont_VCL.diff and dejavufont_helpcontet_css.diff
respectively). 

Created attachment 34262 [details]
Updated DejaVu 2_3

Updated patch:
* Force DejaVu fonts instead of Bitsteram Vera, but not to replace it
* Special Greek font order (requested in:
http://qa.openoffice.org/issues/show_bug.cgi?id=61273)

Created attachment 34542 [details]
Updated DejaVu fonts (2.3), updated patch - works with 2.0.2 M5

.

I'm splitting this issue up into an installation/extras task ("replace the
fonts") and a configuration change ("use the fonts" => issue 64330).

ih->mh: you did check in the bitstream fonts, please replace them as requested here.

2.0.3 is no longer realistic target.

Could you explain your decision? The required patch has attached to this issue...
Tha another part of this issue under issue 64330 is already in the stream...

kami: we can't replace so basic thing like the default fonts so close to the
release (think of possible things that could break!).

We should do this very early in 2.0.4 stage.

I am so sad, because the solution was available before release of 2.0.2. OK
2.0.2 was not realistic, but 3 month later when patch available, testbuilds (at
ftp://ftp.fsf.hu/OpenOffice.org_hu/devel/OOB680_m5_Premium and
ftp://ftp.fsf.hu/OpenOffice.org_hu/devel/OOB680_m5/) work well. So we lost
another 3 month again :o(

Can anyone do the integration work in his CWS?
Thanks,
KAMI

*** Issue 67559 has been marked as a duplicate of this issue. ***

Created attachment 45053 [details]
Updated to 2.16

review is in progress, please stay tuned.

.

Planning integration into cws symex.

IS -> HDU: My part in scp2 is fixed. Please deliver the fonts files from the cvs
modules to <common.pro>/pck.<minor>.
(I saved the font files temporarely in
symex/SRC680/src.236/instset_native/common.pro/bin/fonts)

Done in CWS symex.

@ES: please verify in CWS symex

@hdu: DejaVu releases are generally made each 4 to 6 weeks. I would like to
know, if you would regularly update it in OOo source? Before each OOo release
for example.

@timar: though it would be good idea to always have the latest version one has to consider the 
overhead involved to make it happen:
- making the child-work-space
- developer testing it
- building testable versions on all mainstream platforms
- testing these manually and automatically
- integrating the result into the master
- testing again after integration

That's quite an effort, especially when considering that most users of OOo+DejaVu fonts would 
probably not notice any difference in their daily work. The priority of integrating updated fonts depends 
also on the issues which can be solved by this and the priority of these issues.

New DejaVu versions often include whole new unicode blocks so there are
definitely user-visible changes in them, and  never refreshing the fonts is not
a good idea.

The refresh rate however is open to discussion IMHO. While refreshing every dot
release would be nice it may not be an efficient resource use.

@nmailhot: Yes, of course. Support for more unicodes is a good argument for a refresh. Especially if an 
OOo-localization project benefits from the new glyphs. The refresh will be triggered by a new entry in the 
issuezilla system, if the severity of the issue is high enough.

VERIFIED

Seen in MWS, closing the verified issue.