Re: Encryption

Peter, which one is broken, forrest CVS or fop CVS? On 18.03.2003 08:30:47 Peter B. West wrote: > There's a slight problem here. My files can only be built successfully > with a mod to forrest.build.xml that copies the contents of > resources/scripts into context. If forrestbot is building of

Re: XML FOP: Licensing issues with hyphenation pattern files

Thanks, Greg and Nicola, for your answers. I've already sent the form to the person I mentioned. Now that most of my questions have been resolved I'm off to "distribute" quite a bunch of these forms to all the various copyright holders. After it has been suggested that every single file submitted

Re: Encryption

Victor, There's a slight problem here. My files can only be built successfully with a mod to forrest.build.xml that copies the contents of resources/scripts into context. If forrestbot is building off CVS with a slightly elderly version (and I understand the current CVS is going to be a litt

RE: Encryption

Keiron Liddle wrote: > > Peter, Keiron: how is the web site updated? I thought there was a > > cron job every few hours? > > Currently it only updates the site here: > http://forrestbot.cocoondev.com (seems to > be down at the moment) > From this site you can update the main site by entering the c

Named Destinations

Hi all, I'm really glad to see that in 0.20.5 it will be possible to create named destinations in PDF. I have some small sugestions about this functionality. I'm using Acrobat Reader 5.1 and I was surprised to find out that the url syntax '.pdf#dest=' wasn't working for me. I've looked deeper int

cvs commit: xml-fop/src/documentation/content/xdocs resources.xml

vmote 2003/03/17 09:10:39 Modified:src/documentation/content/xdocs resources.xml Log: Add reference to Mogwai project (Oki dot-matrix renderer), based on discussion today on the user mailing list. Revision ChangesPath 1.7 +5 -0 xml-fop/src/documentation/cont

RE: XML FOP: Licensing issues with hyphenation pattern files

Jeremias Maerki wrote: > And then there's the files from the original TeX distribution by Donald > Knuth which are assumed to be in the public domain but with certain > restrictions (modified file shall not contain the same filename as the > original). Problem there is that there is not really som

Re: XML FOP: Licensing issues with hyphenation pattern files

I've just received that email. The original author is willing to fax in a grant. Question now: Where can I find the form? I've only found the one for committers. Thanks a lot! On 17.03.2003 15:23:55 Jeremias Maerki wrote: > I've received an email a few minutes ago from a FOP contributor telling >

AW: Embedding fonts!

I'm not sure, but I remember we had a similar problem: Our corporate fonts were replaced by Acrobat with built-in fonts, since the font names in the PDF had a prefix like yours. So Acrobat could not find a font like "023442-Corporate12Bold". Try creating the font metrics file using that option. M

Re: XML FOP: Licensing issues with hyphenation pattern files

There's another IMO: Clause 7 expects a restriction that the ASL can't provide. On 17.03.2003 14:32:16 Dirk-Willem van Gulik wrote: > See below the Latex License. > > http://www.latex-project.org/lppl.html > > It seems to me that clause '8.B" makes this license more restrictive than > the

SV: Embedding fonts!

No, I didn't. Should I have done that? /Uwe -Ursprungligt meddelande- Från: Müller, Markus [mailto:[EMAIL PROTECTED] Skickat: den 17 mars 2003 11:40 Till: [EMAIL PROTECTED] Ämne: AW: Embedding fonts! Hi, How did you create the font metrics files? Did you use the option "-enc ansi" ? M

Re: XML FOP: Licensing issues with hyphenation pattern files

Thanks, Steven and Dirk for responding! On 17.03.2003 14:28:44 Dirk-Willem van Gulik wrote: > > > > Before we start here's a little background on the hyphenation stuff: > > > Our hyphenation file are XML files that are derived from TeX hyphenation > > Under what license where the original TeX fi

AW: Embedding fonts!

Hi, How did you create the font metrics files? Did you use the option "-enc ansi" ? Markus $> -Ursprüngliche Nachricht- $> Von: Uwe Klosa [mailto:[EMAIL PROTECTED] $> Gesendet: Montag, 17. März 2003 11:33 $> An: [EMAIL PROTECTED]; [EMAIL PROTECTED] $> Betreff: Embedding fonts! $> $> $

Re: XML FOP: Licensing issues with hyphenation pattern files

Folks, See below the Latex License. http://www.latex-project.org/lppl.html It seems to me that clause '8.B" makes this license more restrictive than the ASF license - and we thus should not allow code(fragements) which are under this license in downloads from ASF infrastructure. Or am

Re: XML FOP: Licensing issues with hyphenation pattern files

> > Before we start here's a little background on the hyphenation stuff: > > Our hyphenation file are XML files that are derived from TeX hyphenation Under what license where the original TeX files ? > > 2. If the former (of [1]) is true, we need a grant from the copyright > > holder of the orig

Stylesheet Attribute Required.

Hi all, I had to check this error out, and a while ago Oleg has helped me for trying to find it. But it didn't work back then... Now the error you get when using xalan transformer : stylesheet requires version, even when it set is solved very simple: just set .setNamespaceAware(true); and the pr

Re: logo contest

Peter B. West wrote: Let's do some elimination rounds. Everyone pick a small number of favourites, say 3. Eliminate anything that doesn't get 2 votes. Do the same, specifying 2 favourites. Eliminate. Then vote for 1 logo. Most votes wins. In the event of a tie, there's a run-off for the w

Embedding fonts!

Hi, I'm using embedded fonts in fop. That is working fine. But if I want to edit the resulting pdf files with Acrobat, the font names aren't correct in the file. I'm getting 1Eec24TimesNewRoman or 2Ef1d7TimesNewRoman where it should be TimesNewRoman. Why creates fop theses font names? Has anyone t

DO NOT REPLY [Bug 18058] New: - Error fetching Image from URL

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bu