Re: Mac Font problem
On Nov 20, 2007, at 07:56, Raphael Parree wrote: Hi I have a problem with a font on a Mac…on my PC everything seems to work but on the Macs uses by our publishing department the Courier New font does not work. It is installed on the Mac (True Type font). I am working with rev 592554 (6 nov) and use the auto detect feature. I have tried deleting the cache file as that often helps on ,my PC after using new fonts or updating FOP. I saw some posts about true type fonts on a Mac posted in feb 2006 (http:// www.nabble.com/TTFReader-and-MacOsX-.ttf-fonts- tf1139715.html#a2986169) I'm also on Mac, and noticed the same effect. Haven't looked into the exact cause, though... One possible workaround, until someone decides to get to the bottom of this: Mac OS X also supports Windows TTFs, so in the worst case, you could maybe try to replace the native Mac TTF with the Windows TTF. Untested though, can't say for sure it will work. HTH! Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mac Font problem
Hi, I have a problem with a font on a Mac.on my PC everything seems to work but on the Macs uses by our publishing department the Courier New font does not work. It is installed on the Mac (True Type font). I am working with rev 592554 (6 nov) and use the auto detect feature. I have tried deleting the cache file as that often helps on ,my PC after using new fonts or updating FOP. I saw some posts about true type fonts on a Mac posted in feb 2006 (http://www.nabble.com/TTFReader-and-MacOsX-.ttf-fonts-tf1139715.html#a29861 69) Anybody any clues? Tx., Raphael
Re: basic-link internal-destination wrong page
Thanks for looking at it with me. Not meaning to be rude, but I won't be sending you any FO file. Please follow my reasoning below: I've tried the fo with 0.20.5 and it's working fine as well. And as you've also checked with 0.92beta and 0.93, so now I'll try to have a look at the modified version of our 0.92beta. I'll keep you posted if any findings might have caused this, for your information. Thank you, William Jeremias Maerki wrote: I've done a quick test shows that this should work just fine in 0.93, but it also works fine for me in 0.92beta. Maybe you've made a mistake somewhere. So again, please attach a (preferably small) FO file that demonstrates your problem. Jeremias Maerki On 19.11.2007 11:15:58 wliem wrote: Thanks Jeremias, It happens that the basic-link points to page 1 in the next page-sequence rather than the first page. Table of Content Introduction 1 Content ...2 ### Actual Content of Page 1 abcdef Actual Content of Page 2 ghijkl Another Content with Page number set to 1 mnopqrs It happens when I click Introduction, it links to 'mnopqrs' instead of 'abcdef' even though the block id links to 'abcdef'. I know that I have to follow on the version upgrade to find the best solution. But do you have any idea which version has started to accommodate this? Many thanks, wliem We have no idea what you hacked into your customized version. You'd better try to work with standard XSL-FO than to coerce FOP into doing what you expect. Maybe you should start by explaining the problem you'd like solved in the first place. It could be that you simply don't know about some funny little detail that would have solved your problem easily. Attach a (preferably small) FO file that demonstrates the problem. That's the easiest way to get us to look into a problem. Otherwise, you just get some not really helpful answers like mine here. :-) BTW, I've explained it once before last week: It's generally a bad/risky idea to hack some private functionality into FOP and not publish it. Mainstream FOP development goes on and you may lose your investment in your code because suddenly, you can't easily upgrade anymore. Please work with us and we'll find the best solution together. That way you can protect your investments. I know, sometimes way may not be as responsive as one might wish. But if that happens, just keep bugging us. An issue may simply have slipped through the cracks. And yes, please upgrade from 0.92beta. ;-) Especially, since we have full support for internal destinations now. Jeremias Maerki On 19.11.2007 04:35:32 william wrote: Hi, We're currently using 0.92beta. We have done some customization to the fop version (in case you offer me to upgrade) The problem that I have currently is that: For the purpose of the pdf output, I used initial-page-number = 1 to reset the page number and start from 1 somewhere within the file. As a result, some basic-link internal-destination does not point to the right place even though the id has already been specified to the right position. Suggestions are welcome. Thanks a lot, wliem - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- William LiemEmail: [EMAIL PROTECTED] Allette Systems Pty Ltd. Level 2, 73 Union St Pyrmont NSW 2009 Australia Tel: +61 2 9660 8866 Fax: +61 2 9660 8869 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Check "response" in fo:external-graphic
Hi everybody, I want to add some images to my pdf. Those images where genereated by an servlet - so far so good. My problem is that the webapplication runs on 2 clusters :( My code looks like this: Is there a possibility to check the result of this request. Because if I don't get an image by using servletURL1 I have to change to servletURL2. Thanks in advance! -- View this message in context: http://www.nabble.com/Check-%22response%22-in-fo%3Aexternal-graphic-tf4836367.html#a13836181 Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Loadind Fonts as Resource in 0.94 or Trunk
Hi, The Font Loading has changed singnificant in the version 0.94. I have some problems with new Implementation. I used 0.93 and has my own URIResolver configured, that has me allowed to load my Fonts as Resource. Now Fop awaits the URLs (Paths) to resolve to find the Fonts. But i have not found how can i do it by my self. Old method, just set URIResolver not worked for me any more. Is it possible to load fonts as resource? thans a lot Dmitri
Re: basic-link internal-destination wrong page
I've done a quick test shows that this should work just fine in 0.93, but it also works fine for me in 0.92beta. Maybe you've made a mistake somewhere. So again, please attach a (preferably small) FO file that demonstrates your problem. Jeremias Maerki On 19.11.2007 11:15:58 wliem wrote: > Thanks Jeremias, > > It happens that the basic-link points to page 1 in the next page-sequence > rather than the first page. > > Table of Content > Introduction 1 > Content ...2 > > ### > Actual Content of Page 1 > abcdef > > Actual Content of Page 2 > ghijkl > > Another Content with Page number set to 1 > mnopqrs > > > It happens when I click Introduction, it links to 'mnopqrs' instead of > 'abcdef' even though the block id links to 'abcdef'. > I know that I have to follow on the version upgrade to find the best > solution. But do you have any idea which version has > started to accommodate this? > > Many thanks, > wliem > > > We have no idea what you hacked into your customized version. You'd > > better try to work with standard XSL-FO than to coerce FOP into doing > > what you expect. Maybe you should start by explaining the problem you'd > > like solved in the first place. It could be that you simply don't know > > about some funny little detail that would have solved your problem > > easily. Attach a (preferably small) FO file that demonstrates the > > problem. That's the easiest way to get us to look into a problem. > > Otherwise, you just get some not really helpful answers like mine here. > > :-) > > > > BTW, I've explained it once before last week: It's generally a bad/risky > > idea to hack some private functionality into FOP and not publish it. > > Mainstream FOP development goes on and you may lose your investment in > > your code because suddenly, you can't easily upgrade anymore. Please > > work with us and we'll find the best solution together. That way you can > > protect your investments. > > > > I know, sometimes way may not be as responsive as one might wish. But if > > that happens, just keep bugging us. An issue may simply have slipped > > through the cracks. > > > > And yes, please upgrade from 0.92beta. ;-) Especially, since we have > > full support for internal destinations now. > > > > Jeremias Maerki > > > > > > > > On 19.11.2007 04:35:32 william wrote: > >> Hi, > >> > >> We're currently using 0.92beta. We have done some customization to the > >> fop version (in case you offer me to upgrade) > >> > >> The problem that I have currently is that: > >> For the purpose of the pdf output, I used initial-page-number = 1 to > >> reset the page number and start from 1 somewhere within the file. > >> As a result, some basic-link internal-destination does not point to the > >> right place even though the id has already been specified to the right > >> position. > >> > >> Suggestions are welcome. > >> > >> Thanks a lot, > >> wliem - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: basic-link internal-destination wrong page
Thanks Jeremias, It happens that the basic-link points to page 1 in the next page-sequence rather than the first page. Table of Content Introduction 1 Content ...2 ### Actual Content of Page 1 abcdef Actual Content of Page 2 ghijkl Another Content with Page number set to 1 mnopqrs It happens when I click Introduction, it links to 'mnopqrs' instead of 'abcdef' even though the block id links to 'abcdef'. I know that I have to follow on the version upgrade to find the best solution. But do you have any idea which version has started to accommodate this? Many thanks, wliem > We have no idea what you hacked into your customized version. You'd > better try to work with standard XSL-FO than to coerce FOP into doing > what you expect. Maybe you should start by explaining the problem you'd > like solved in the first place. It could be that you simply don't know > about some funny little detail that would have solved your problem > easily. Attach a (preferably small) FO file that demonstrates the > problem. That's the easiest way to get us to look into a problem. > Otherwise, you just get some not really helpful answers like mine here. > :-) > > BTW, I've explained it once before last week: It's generally a bad/risky > idea to hack some private functionality into FOP and not publish it. > Mainstream FOP development goes on and you may lose your investment in > your code because suddenly, you can't easily upgrade anymore. Please > work with us and we'll find the best solution together. That way you can > protect your investments. > > I know, sometimes way may not be as responsive as one might wish. But if > that happens, just keep bugging us. An issue may simply have slipped > through the cracks. > > And yes, please upgrade from 0.92beta. ;-) Especially, since we have > full support for internal destinations now. > > Jeremias Maerki > > > > On 19.11.2007 04:35:32 william wrote: >> Hi, >> >> We're currently using 0.92beta. We have done some customization to the >> fop version (in case you offer me to upgrade) >> >> The problem that I have currently is that: >> For the purpose of the pdf output, I used initial-page-number = 1 to >> reset the page number and start from 1 somewhere within the file. >> As a result, some basic-link internal-destination does not point to the >> right place even though the id has already been specified to the right >> position. >> >> Suggestions are welcome. >> >> Thanks a lot, >> wliem > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: basic-link internal-destination wrong page
We have no idea what you hacked into your customized version. You'd better try to work with standard XSL-FO than to coerce FOP into doing what you expect. Maybe you should start by explaining the problem you'd like solved in the first place. It could be that you simply don't know about some funny little detail that would have solved your problem easily. Attach a (preferably small) FO file that demonstrates the problem. That's the easiest way to get us to look into a problem. Otherwise, you just get some not really helpful answers like mine here. :-) BTW, I've explained it once before last week: It's generally a bad/risky idea to hack some private functionality into FOP and not publish it. Mainstream FOP development goes on and you may lose your investment in your code because suddenly, you can't easily upgrade anymore. Please work with us and we'll find the best solution together. That way you can protect your investments. I know, sometimes way may not be as responsive as one might wish. But if that happens, just keep bugging us. An issue may simply have slipped through the cracks. And yes, please upgrade from 0.92beta. ;-) Especially, since we have full support for internal destinations now. Jeremias Maerki On 19.11.2007 04:35:32 william wrote: > Hi, > > We're currently using 0.92beta. We have done some customization to the > fop version (in case you offer me to upgrade) > > The problem that I have currently is that: > For the purpose of the pdf output, I used initial-page-number = 1 to > reset the page number and start from 1 somewhere within the file. > As a result, some basic-link internal-destination does not point to the > right place even though the id has already been specified to the right > position. > > Suggestions are welcome. > > Thanks a lot, > wliem - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: refsynopsisdiv title not showing up in PDF, fop0.94
This seems to be a DocBook question. You'd better throw your question in that arena since the problem seems to be located in the XSLT stage, before FOP even gets active. Jeremias Maerki On 19.11.2007 00:30:18 gfx_dude wrote: > > The title of a refsynopsisdiv section does not show up in a FOP generated > PDF. It does show up in generated XHTML, and other reference section titles > show up, i.e. refsect1 section titles. > > > > Synopsis > > > Synopsis doesn't appear in the .fo or the PDF. It looks like the fo:block > might be set up correctly, but there's no text in the block. I'm guessing > its a problem in the refentry.xsl file in the fo directory. I've been > looking at this for several days, any ideas? Hopefully its something simple. > > Thanks in advance > > gfx_dude > -- > View this message in context: > http://www.nabble.com/refsynopsisdiv-title-not-showing-up-in-PDF%2C--fop0.94-tf4832373.html#a13825362 > Sent from the FOP - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
