Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index

[tdf-discuss] Re: ANN: ODF 1.2 Candidate OASIS Standard Enters 60-Day Public Review, prerequisite for balloting as OASIS Standard



Charles-H. Schulz wrote:

We're not talking about the same use cases. Embedding fonts create a
whole lot of different problems in terms of interoperability.

But you're welcome to join the ODF TC, even as an individual.


I believe that there are many interoperability problems. 

But if ODF is not going to support font embedding in the near future then it
is no alternative to the MS file formats for files where fonts are important
such as presentations and vector art.

Given this position from OASIS, LO developers should concentrate ASAP on
adding the ability to embed fonts in MS formats (preferably the newer XML
based formats) which already have this function.

--
View this message in context: 
http://nabble.documentfoundation.org/ANN-ODF-1-2-Candidate-OASIS-Standard-Enters-60-Day-Public-Review-prerequisite-for-balloting-as-OASISd-tp3102710p3105011.html
Sent from the Discuss mailing list archive at Nabble.com.

-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.documentfoundation.org/www/discuss/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.