On Jun 7, 2011, at 6:54 PM, robert_w...@us.ibm.com wrote: > Dave Fisher <dave2w...@comcast.net> wrote on 06/07/2011 09:23:25 PM: > >> >> Sure. Hi everyone (maybe the people that Rob knows should introduce >> themselves as well - some of us are new to the community.) >> >> My name is David Fisher. I have been in the software industry for >> over 30 years. I've worked in many computer languages - FORTRAN, PL/ >> 1, C, C++, Postscript, Java, Basic, etc., etc. I wrote a PDF >> producer in C++ in the early 90's. At my direction as a project >> manager we developed the ability to produce PowerPoint output using >> Apache POI. This was contributed back to the project and this >> started my involvement with the ASF. >> >> I am very interested in the synergies and advantages to the OOo >> community that full cross compatibility with Microsoft Office >> documents could provide - particularly with workbooks. >> >> I look forward to working with the ODF Toolkit. I also would like to >> see what I can do to help with fonts, EPS, PDF and print files. >> >> The ASF has sponsored several projects which have become essential >> tools at work - Tomcat, Lucene and POI especially. >> >> I am speaking as individual and not for my corporate employer (not a >> software company.) >> > > Hi Dave, that is a great skill set. Do you know anything about font > embedding? Not in PDF, but how it should be done in editable documents, > respecting font policies, etc? > > This issue is one of our top ODF feature requests, and a quick search > shows that it is a popular request for OOo as well: > > http://openoffice.org/bugzilla/show_bug.cgi?id=20370 > > A feature like this greatly improves cross-OS document interop.
Thank you, and yes you are correct handling of fonts is a very tricky issue that touches on accessibility issues as well as translation and terms of art. I have not thought deeply about embedding in some time. I think that it is more important to find a balance between two factors. (1) FInding a font on the user's machine that is "close" to the producer/designer's. Meaning similar/equivalent character set, font style, and metrics. (2) Regulators require consistently formatted documents to the level of a line break, but not necessarily the font. (Correct me if I am wrong.) So, I think that embedding the intended font metrics within a document is more important than embedding particular fonts. Less license issues that way as well. I know that the ASF has license to the Adobe Base 14 AFM files. I don't know what this means for standards, etc, this I would like to learn. I do have a copy of FontForge and really liked Fontographer. Point me at the "state of the art" and I am good to go. I understand why you aren't talking PDF sub-setting as that is more about total preservation of a print form. I guess in Impress the font is the intent and this is more in play. As a print format embedding the font file should not be an issue. I could help define fonts and I do have an understanding of the Type 1 and other formats. I would need help with multi-byte fonts. Let's get the podling approved and get to work! BTW - In reality lack of a font license is a major issue in the re-use and editing of previously published documents. I have this issue in a potential work project right now. These issues require a pragmatic approach. An Apache Open Office ought to allow the user to specify how to they prefer to handle font translations. (is that font and translation?) This is enough for now. Best Regards, Dave > > Regards, > > -Rob > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
