Re: Encoding issue in PDFOutputIntent.java
You're running Windows! ;-) On Apr 5, 2006, at 10:48 PM, Jeremias Maerki wrote: Fixed. Don't know how I managed to type this special apostrophe. On 06.04.2006 00:29:31 Manuel Mall wrote: I am getting the warning below when compiling the latest trunk Manuel [javac] /home/mm/fop-trunk/src/java/org/apache/fop/pdf/ PDFOutputIntent.java:121: warning: unmappable character for encoding UTF8 [javac] * document�s source colors to output device colorants. Jeremias Maerki Clay Leeds [EMAIL PROTECTED] My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet
Re: Encoding issue in PDFOutputIntent.java
On Apr 5, 2006, at 11:14 PM, Clay Leeds wrote: You're running Windows! ;-) Seriously, I suspect you copied something w 'smart quotes' from MS Word... Clay Leeds [EMAIL PROTECTED] My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet
Re: Encoding issue in PDFOutputIntent.java
Hmm, you could even be right. But it was probably Acrobat Reader, not Word. *g* On 06.04.2006 15:41:34 Clay Leeds wrote: On Apr 5, 2006, at 11:14 PM, Clay Leeds wrote: You're running Windows! ;-) Seriously, I suspect you copied something w 'smart quotes' from MS Word... Jeremias Maerki
How about a release?
We originally wanted to do a release much earlier but I was always in the middle of something and I think I'm simply the only one who can allocate enough time to do an actual release (prove me wrong, please). I think I can make time next week to do a release of FOP and XML Graphics Commons. FOP Trunk is currently in pretty good condition, the new API is established and documented. I imagine a 0.92beta (beta only because of the changed API and the many deprecations, PDF and PS output are production-ready IMO), and after waiting for some time for feedback on the API, we could release a 1.0. So if there's nothing that would block a release, I can create a release branch and start a PMC vote for the release. WDYT? Jeremias Maerki
Re: How about a release?
Jeremias Maerki wrote: We originally wanted to do a release much earlier but I was always in the middle of something and I think I'm simply the only one who can allocate enough time to do an actual release (prove me wrong, please). I think I can make time next week to do a release of FOP and XML Graphics Commons. FOP Trunk is currently in pretty good condition, the new API is established and documented. I imagine a 0.92beta (beta only because of the changed API and the many deprecations, PDF and PS output are production-ready IMO), and after waiting for some time for feedback on the API, we could release a 1.0. So if there's nothing that would block a release, I can create a release branch and start a PMC vote for the release. WDYT? Yes I agree completely +1 Chris
Return carriage
Hello all, I started to develop using embebbed FOP just recently and I´m having a problem in a report. The case is that one block field just don´t break the line when the text inside (dinamically loaded) is higher than the page width. Follow the code I´m using: fo:block wrap-option=wrap #if ($testInfo.HBM_Method == TEST) #foreach( $test in $testResults ) $test.VoltageRanges #end #else $summary.TestVoltages #end /fo:block The result I expect was a line like that 1000,1001,1002,1003,1004,1005...and go on But the line just continue as the end of the page simply don´t exist :-o Thanks in advance -- View this message in context: http://www.nabble.com/Return-carriage-t1407358.html#a3789522 Sent from the FOP - Dev forum at Nabble.com.
Re: How about a release?
WDYT? From my perspective as a user, I think it's essential to fix the problem with preserving whitespace after a newline (for pre-style output) before doing another release. -Peter-
Re: How about a release?
On Apr 6, 2006, at 8:55 AM, Chris Bowditch wrote: Jeremias Maerki wrote: We originally wanted to do a release much earlier but I was always in the middle of something and I think I'm simply the only one who can allocate enough time to do an actual release (prove me wrong, please). I think I can make time next week to do a release of FOP and XML Graphics Commons. FOP Trunk is currently in pretty good condition, the new API is established and documented. I imagine a 0.92beta (beta only because of the changed API and the many deprecations, PDF and PS output are production-ready IMO), and after waiting for some time for feedback on the API, we could release a 1.0. So if there's nothing that would block a release, I can create a release branch and start a PMC vote for the release. WDYT? Yes I agree completely +1 Chris I'd like to see a release as well. But is this a new issue? Has it been resolved? On Apr 6, 2006, at 11:50 AM, Peter S. Housel wrote: WDYT? From my perspective as a user, I think it's essential to fix the problem with preserving whitespace after a newline (for pre-style output) before doing another release. -Peter- If it's resolved, then I'd give my +1 to a PMC VOTE. If not, then can it be resolved quickly? If not, then I'd say '+1'. Clay Leeds [EMAIL PROTECTED] My religion is simple. My religion is kindness. -- HH Dalai Lama of Tibet
