RE: Font names...
Thanks Vincent, As always it's a pleasure to use FOP, knowing that the developers are so active at squashing bugs and implementing new features. One of the benefits of OpenSource I suppose. Keep up the good work! Cheers Karl PS, I've just seen Bertrand Delacrétaz' commits in the source. I'll give it a few days then try it out ! :-) -Original Message- From: Vincent Hennebert [mailto:[EMAIL PROTECTED] Sent: Thursday, 21 September 2006 5:22 PM To: fop-users@xmlgraphics.apache.org Subject: Re: Font names... Hi Karl, Karl Roberts a écrit : > Hi Vincent, > >>> This issue will soon disappear. The current font library will be > replaced with another one (FOrayFont), which >>> handles that completely differently. > > Do you know how soon the FOrayFont stuff will be in the trunk? I'm Well, if everything goes right it should be there by the end of this year. > waiting on it to fix the Bug where you can't copy and paste characters > from the PDF document. Actually this does not depend on the integration of FOrayFont. There is another developer (Bertrand Delacrétaz) who will work on this in the next days so the fix should be available soon. > I presume there'll be a big splash when it happens so we'll all know > how to configure it? Copy&paste support won't be configurable. It will simply be available ;-) As for the configuration of fonts, sure, we will try to provide the necessary documentation. Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
Hi Karl, Karl Roberts a écrit : > Hi Vincent, > >>> This issue will soon disappear. The current font library will be > replaced with another one (FOrayFont), which >>> handles that completely differently. > > Do you know how soon the FOrayFont stuff will be in the trunk? I'm Well, if everything goes right it should be there by the end of this year. > waiting on it to fix the Bug where you can't copy and paste characters > from the PDF document. Actually this does not depend on the integration of FOrayFont. There is another developer (Bertrand Delacrétaz) who will work on this in the next days so the fix should be available soon. > I presume there'll be a big splash when it happens so we'll all know how > to configure it? Copy&paste support won't be configurable. It will simply be available ;-) As for the configuration of fonts, sure, we will try to provide the necessary documentation. Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Font names...
Hi Vincent, >> This issue will soon disappear. The current font library will be replaced with another one (FOrayFont), which >> handles that completely differently. Do you know how soon the FOrayFont stuff will be in the trunk? I'm waiting on it to fix the Bug where you can't copy and paste characters from the PDF document. I presume there'll be a big splash when it happens so we'll all know how to configure it? Cheers Karl Roberts NOTICE This e-mail and any attachments are confidential and may contain copyright material of Macquarie Bank or third parties. If you are not the intended recipient of this email you should not read, print, re-transmit, store or act in reliance on this e-mail or any attachments, and should destroy all copies of them. Macquarie Bank does not guarantee the integrity of any emails or any attached files. The views or opinions expressed are the author's own and may not reflect the views or opinions of Macquarie Bank. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
Vincent Hennebert-3 wrote: > > Luis, would you mind summarizing your problems in a Bugzilla entry? So > that we can more easily track them, and ensure they will actually be > corrected in the new font library. Thanks! > Will do... I think it's about time i create a bugzilla login in FOP as it seams that i will be working more and more with it ;) And gratz on all the feedback from you all... Cheers, LF -- View this message in context: http://www.nabble.com/Font-names...-tf2287650.html#a6404011 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
>> Mayhappen the reasons for changing the font names when working with >> full/partial embed fonts aren't relevant anymore... >> >> Would like to take the oportunity to suggest that a switch like "-fullembed" >> (or something like that) be used instead of the "-ansi", as a >> "clarification" of what the switch do. > > Suggestion noted but someone actually has to implement it. Not sure who > that will be. This issue will soon disappear. The current font library will be replaced with another one (FOrayFont), which handles that completely differently. >> P.S.- get rid of the font metrics would just be perfect. Also perfect would There will also be no intermediate XML file anymore, the font file will be directly used. >> be to note in the config file how one wants the font to be placed on the pdf >> (partial embed, full embed or reference only). This possibility will be available. > That's in the works. Date? Unknown. Chances rising in the near future. I > have some insider info about someone who'll have more time to work on > FOP (not me). ;-) Mmmh, I wonder who you're talking about?? Ok, this won't appear in the next release (Fop 0.93) because this is to big of a change. Probably the release after. Luis, would you mind summarizing your problems in a Bugzilla entry? So that we can more easily track them, and ensure they will actually be corrected in the new font library. Thanks! Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
On 18.09.2006 17:05:09 Luis Ferro wrote: > > > Jeremias Maerki-2 wrote: > > > > In that case we cannot use the original font > > name because we don't embed the full font. > > 2 questions then... > > a) What happens if with a partial embed font it's used the same name as the > original font name? I don't know. We're just following the PDF specification: "For a font subset, the PostScript name of the fontthe value of the fonts BaseFont entry and the font descriptors FontName entrybegins with a tag followed by a plus sign (+). The tag consists of exactly six uppercase letters; the choice of letters is arbitrary, but different subsets in the same PDF file must have different tags. For example, EOODIA+Poetica is the name of a subset of Poetica®, a Type 1 font." > b) What happens if with a full embed font (with use of -ansi when building > the metrics) it's used the same name as the original font name? > > The questions have some significance, because the PDF file that resulted > from fop was edited with Acrobat pro 6 (which "unembeds" the font and allows > the edit to continue, showing a warning regarding this) and when it was > tryed to export to ps, acrobat just refused to work because the font's didnt > match (there was a diference between the names like "Arial,light" in the > PDF, when the true font name is "Arial-light"). > > This little diference had no side-effects on the PDF, but forfeited the use > of the PDF for anything. The PDF restarted to work well after we grabed a > font editor and changed in the internal properties of the font the "-" for a > ",". Well, it could be that FOP does something wrong here. We'd have to investigate that closely. Not sure when I'd have time for this. Do you have time? > Mayhappen the reasons for changing the font names when working with > full/partial embed fonts aren't relevant anymore... > > Would like to take the oportunity to suggest that a switch like "-fullembed" > (or something like that) be used instead of the "-ansi", as a > "clarification" of what the switch do. Suggestion noted but someone actually has to implement it. Not sure who that will be. > Cheers, > LF > > P.S.- get rid of the font metrics would just be perfect. Also perfect would > be to note in the config file how one wants the font to be placed on the pdf > (partial embed, full embed or reference only). That's in the works. Date? Unknown. Chances rising in the near future. I have some insider info about someone who'll have more time to work on FOP (not me). ;-) Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
Yes, this way the whole font is embedded but you only have access to the WinAnsi subset of characters. On 18.09.2006 12:28:40 Luis Ferro wrote: > > One of the things that appeared from the properties of the document is the > "actual" font values. > > The config i used is: > kerning="yes" > embed-url="D:\sites\mapaterapeutico\fonts\SWZ721l.TTF"> > > > > And i created the font metrics with the following class call (a short fused > version based on the fop.bat): > > org.apache.fop.fonts.apps.TTFReader -enc ansi %FOP_CMD_LINE_ARGS% > > With those parameters, i assume that the "full" font is embedded... as it is > looselly refered in the import font documentation of fop... > > The actual font parameters aren't setup in the PDF. Mayhappen with the > addition of those "actual" font file, pointing the url file, the PDF could > be editable... > > Just a tought... > > Cheers, > LF > > > > > > Jeremias Maerki-2 wrote: > > > > I assume the problem comes from FOP's embedding only a subset of the > > TrueType font in the PDF. In that case we cannot use the original font > > name because we don't embed the full font. If you have to be able to > > edit the PDF you'd need to embed the full font in which case we could > > use the original name. FOP currently doesn't support that, though. > > > > On 17.09.2006 22:51:41 Luis Ferro wrote: > >> > >> The test is simple... > >> > >> Prepare a font (tested with TTF fonts) for importing, one that has some > >> "attributes" like "light". > >> > >> Make a document which uses that font and produce a PDF. > >> > >> Edit the PDF with acrobat pro. > >> > >> What will happen is that the name the font has isn't the same name as the > >> embed font. > >> > >> The render will work ok, but the edit will mean a "warning" of font to > >> become "unembed". That isn't a problem, except that as the font name is > >> wrong (the font name listed in the pdf doesn't match the font name in the > >> TTF file, what will happen is that acrobat can't find it and allow the > >> "reembed" of it). > >> > >> If needed will post files that exemplify this effect (i'm not sure if > >> this > >> is a FOP problem yet - will do more tests next week). Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
Jeremias Maerki-2 wrote: > > In that case we cannot use the original font > name because we don't embed the full font. 2 questions then... a) What happens if with a partial embed font it's used the same name as the original font name? b) What happens if with a full embed font (with use of -ansi when building the metrics) it's used the same name as the original font name? The questions have some significance, because the PDF file that resulted from fop was edited with Acrobat pro 6 (which "unembeds" the font and allows the edit to continue, showing a warning regarding this) and when it was tryed to export to ps, acrobat just refused to work because the font's didnt match (there was a diference between the names like "Arial,light" in the PDF, when the true font name is "Arial-light"). This little diference had no side-effects on the PDF, but forfeited the use of the PDF for anything. The PDF restarted to work well after we grabed a font editor and changed in the internal properties of the font the "-" for a ",". Mayhappen the reasons for changing the font names when working with full/partial embed fonts aren't relevant anymore... Would like to take the oportunity to suggest that a switch like "-fullembed" (or something like that) be used instead of the "-ansi", as a "clarification" of what the switch do. Cheers, LF P.S.- get rid of the font metrics would just be perfect. Also perfect would be to note in the config file how one wants the font to be placed on the pdf (partial embed, full embed or reference only). -- View this message in context: http://www.nabble.com/Font-names...-tf2287650.html#a6365457 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
One of the things that appeared from the properties of the document is the "actual" font values. The config i used is: And i created the font metrics with the following class call (a short fused version based on the fop.bat): org.apache.fop.fonts.apps.TTFReader -enc ansi %FOP_CMD_LINE_ARGS% With those parameters, i assume that the "full" font is embedded... as it is looselly refered in the import font documentation of fop... The actual font parameters aren't setup in the PDF. Mayhappen with the addition of those "actual" font file, pointing the url file, the PDF could be editable... Just a tought... Cheers, LF Jeremias Maerki-2 wrote: > > I assume the problem comes from FOP's embedding only a subset of the > TrueType font in the PDF. In that case we cannot use the original font > name because we don't embed the full font. If you have to be able to > edit the PDF you'd need to embed the full font in which case we could > use the original name. FOP currently doesn't support that, though. > > On 17.09.2006 22:51:41 Luis Ferro wrote: >> >> The test is simple... >> >> Prepare a font (tested with TTF fonts) for importing, one that has some >> "attributes" like "light". >> >> Make a document which uses that font and produce a PDF. >> >> Edit the PDF with acrobat pro. >> >> What will happen is that the name the font has isn't the same name as the >> embed font. >> >> The render will work ok, but the edit will mean a "warning" of font to >> become "unembed". That isn't a problem, except that as the font name is >> wrong (the font name listed in the pdf doesn't match the font name in the >> TTF file, what will happen is that acrobat can't find it and allow the >> "reembed" of it). >> >> If needed will post files that exemplify this effect (i'm not sure if >> this >> is a FOP problem yet - will do more tests next week). > > > > Jeremias Maerki > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Font-names...-tf2287650.html#a6361198 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
I assume the problem comes from FOP's embedding only a subset of the TrueType font in the PDF. In that case we cannot use the original font name because we don't embed the full font. If you have to be able to edit the PDF you'd need to embed the full font in which case we could use the original name. FOP currently doesn't support that, though. On 17.09.2006 22:51:41 Luis Ferro wrote: > > The test is simple... > > Prepare a font (tested with TTF fonts) for importing, one that has some > "attributes" like "light". > > Make a document which uses that font and produce a PDF. > > Edit the PDF with acrobat pro. > > What will happen is that the name the font has isn't the same name as the > embed font. > > The render will work ok, but the edit will mean a "warning" of font to > become "unembed". That isn't a problem, except that as the font name is > wrong (the font name listed in the pdf doesn't match the font name in the > TTF file, what will happen is that acrobat can't find it and allow the > "reembed" of it). > > If needed will post files that exemplify this effect (i'm not sure if this > is a FOP problem yet - will do more tests next week). Jeremias Maerki - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Font names...
Luis Ferro wrote: > > The test is simple... > Not that simple i'm afraid... i think i'm in a goose chase here regarding font names... The font that is in use by FOP (thru the config options) either gets a diferent name in windows or isn't recognized by it (even thru it's a ttf font, albeit can be in a format that windows can't use). So, naturally all tries to edit the document in Acrobat are doomed to fail. Cheers, LF -- View this message in context: http://www.nabble.com/Font-names...-tf2287650.html#a6360276 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
