https://bugs.documentfoundation.org/show_bug.cgi?id=161941
--- Comment #8 from V Stuart Foote <[email protected]> --- (In reply to Buovjaga from comment #7) > (In reply to Eyal Rozenberg from comment #6) > > (In reply to Caolán McNamara from comment #5) > > > Google found it worthwhile to create these > > > metrically equivalent fonts for compatibility purposes. > > > > If we knew what these purposes were, and what they wanted compatibility with > > - we could consider that. But on principle, it is not reasonable for us to > > add files to our distribution just because we were told someone at (the > > 180,000-person company) Google decided they were useful... :-( > > Indeed. There is no documentation, blog post or anything explaining how this > DocRepair project came about. Google is all about data mining, so surely > they might give an explanation on why they decided to do this. Is it even a google sponsored project? Looks to be on github https://github.com/orgs/docrepair-fonts/repositories Look in the repos of the individual font for replacement/usage goals, most with intent to avoid reflow of OOXML (ISO 29500) documents. To obtain more details, and an idea if TDF and our LibreOffice/Document Liberation projects should actively participate, i.e. a home for 'OpenSymbol' perhaps someone might contact project lead, Adam Twardoch. Who does not look to be a Google employee ;-) -- You are receiving this mail because: You are the assignee for the bug.
