gzilla/show_bug.cgi?id=30983
The wrong pdf document encoding
Summary: The wrong pdf document encoding
Product: Fop
Version: 0.15
Platform: PC
OS/Version: Other
Status: NEW
Severity: Normal
Priority: Other
Com
Peter B. West wrote:
In http://xml.apache.org/fop/design/alt.design/index.html there occurs
the following link:
http://marc.theaimsgroup.com/%3Fl=fop-dev%26m=103890259919360%26w=2";>
The question mark and ampersand are encoded as expected. When I hover
on this link in Mozilla, I get:
http://mar
Fops,
In http://xml.apache.org/fop/design/alt.design/index.html there occurs
the following link:
http://marc.theaimsgroup.com/%3Fl=fop-dev%26m=103890259919360%26w=2";>
The question mark and ampersand are encoded as expected. When I hover
on this link in Mozilla, I get:
http://marc.theaimsgroup.
e which is used in "Trey's" word
There is no single quote.
^^
Trey’s Best
Well, MS Word is lying: the XML is probably encoded in Windows CP1252
(or so). The fancy apostrophe (IIRC or ‘) is not a valid
XML character in ISO-8859-1 encodi
Hi all,
I have a fo file which has some special characters,
which are not being parsing by FOp and throwing
"Invalid byte 1 of 1-byte UTF-8 sequence" exception.
Can any one tell me how to fix this problem.please
have a look at the Fo file.It is throwing exception at
single quote which is used in "T
Peter B. West wrote:
> Ok, so how do we drive this thing? Is it zoomable? I couldn't find
> pietsch on there either.
Sorry, I meant to show the path (it took a while to figure out):
Joerg gave us:
http://cvs.apache.org/~sgala/nightmap.html
Then (hoping to find something instructive) look at:
h
J.Pietschmann wrote:
> BTW, I notice the absence of you and Peter from
> http://cvs.apache.org/~sgala/nightmap.html
OK, I should be on there the next time the map is regenerated. Now that you
guys know how to get here, come on over!
Victor Mote
---
J.Pietschmann wrote:
Victor Mote wrote:
BTW, I notice the absence of you and Peter from
http://cvs.apache.org/~sgala/nightmap.html
Ok, so how do we drive this thing? Is it zoomable? I couldn't find
pietsch on there either.
Peter
--
Peter B. West http://www.powerup.com.au/~pbwest/resume.html
Victor Mote wrote:
I never bit the emacs bullet, and don't directly know the impact there.
GNU emacs 21 knows about UTF-8. Unfortunately, the NT port seems to
be less rock solid than usual, I got the first emacs crashes since
I abandoned Solaris 2.1 in, well, lets say an epoch or two ago.
BTW, I no
cters as well,
but the UTF-8 range 00-7F always represents a single-byte character, so
there should be no ASCII nulls (at least not as the result of an
ASCII-to-UTF-8 conversion).
Yes. Now that I think a bit more about it, UTF8 guarantees that all
non-ASCII characters will have the 8th bit set; that&
Peter B. West wrote:
> (I wouldn't say it was heated.) I am curious about the impact of
> someone working without any formal IDE, and just using (X)Emacs and JDEE
> for development. As far as I know, XEmacs does not support Unicode, but
> if the non-ASCII characters were restricted to comments,
Keep a list of Java source files which need a different encoding
and force ISO-8859-1 on the rest
c) Switch to UTF-8. Eclipse can deal with UTF-8. Users of other
IDEs are, to a large part, screwed.
I already chose option #3 for the files in question (probably 2 weeks ago).
If java source file
e files?
> b) Keep a list of Java source files which need a different encoding
>and force ISO-8859-1 on the rest
> c) Switch to UTF-8. Eclipse can deal with UTF-8. Users of other
>IDEs are, to a large part, screwed.
I already chose option #3 for the files in question (probably 2
Le Vendredi, 4 juil 2003, à 21:12 Europe/Zurich, J.Pietschmann a écrit :
Bertrand Delacretaz wrote:
Sure - it is by accident that comments in the jfor source code
contains non-ASCII chars (in people's names IIRC).
OOps, I didn't think about that. We could
What I meant is that I think (or rath
on-western contributors
who might want to have their names in their native script
in the files?
b) Keep a list of Java source files which need a different encoding
and force ISO-8859-1 on the rest
c) Switch to UTF-8. Eclipse can deal with UTF-8. Users of other
IDEs are, to a large par
Le Jeudi, 3 juil 2003, à 21:16 Europe/Zurich, J.Pietschmann a écrit :
...And, uh, comment language is *english*, guys :-)
Sure - it is by accident that comments in the jfor source code contains
non-ASCII chars (in people's names IIRC).
No problem in removing the accents!
-Bertrand
--
Christian Geisert wrote:
> > Java source is Unicode, and I don't think the encoding would matter, but
>
> Java source is whatever the platform encoding is (see file.encoding
> system property) so the best thing is to avoid chars > 127 at all
> (use \u instead) ...
Christian Geisert wrote:
Java source is whatever the platform encoding is (see file.encoding
system property) so the best thing is to avoid chars > 127 at all
(use \u instead) ... uh this won't work in this case as
these are comments. Maybe there's a workaround for special frenc
know that.
Java source is Unicode, and I don't think the encoding would matter, but
Java source is whatever the platform encoding is (see file.encoding
system property) so the best thing is to avoid chars > 127 at all
(use \u instead) ... uh this won't work in this case as
these a
gzilla/show_bug.cgi?id=17828
Encoding problem with Type 1 fonts
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Reso
gzilla/show_bug.cgi?id=17828
Encoding problem with Type 1 fonts
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|I
gzilla/show_bug.cgi?id=17828
Encoding problem with Type 1 fonts
--- Additional Comments From [EMAIL PROTECTED] 2003-03-10 15:51 ---
When I'm using True Type fonts everything is OK. Problem is only with Type 1. I
had spent a long time with reading bugs and documentation (also FAQ) a
gzilla/show_bug.cgi?id=17828
Encoding problem with Type 1 fonts
--- Additional Comments From [EMAIL PROTECTED] 2003-03-10 15:17 ---
Created an attachment (id=5246)
Includes userconfig, sample FO and font
-
To unsubscribe,
gzilla/show_bug.cgi?id=17828
Encoding problem with Type 1 fonts
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RESOLVED
Reso
gzilla/show_bug.cgi?id=17828
Encoding problem with Type 1 fonts
Summary: Encoding problem with Type 1 fonts
Product: Fop
Version: 0.20.4
Platform: PC
OS/Version: Windows NT/2K
Status: NEW
Severity: Blocker
Priority:
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |RE
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
--- Additional Comments From [EMAIL PROTECTED] 2002-11-29 07:22 ---
Moved the discussion of the image URL resolution issue to a new bug
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
--- Additional Comments From [EMAIL PROTECTED] 2002-11-28 14:01
---
I just had a look a the current source with regards to relative URLs.
The relative part is done with a URL.getFile() which retur
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
--- Additional Comments From [EMAIL PROTECTED] 2002-11-19 01:20 ---
Christian,
thanks for accepting and committing my patch. I hope to be able to contribute
more in the future.
Regarding the res
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
--- Additional Comments From [EMAIL PROTECTED] 2002-11-18 15:09
---
Thanks for your contribution.
I've committed everything except the change concerning relative URIs
(current code works f
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
[EMAIL PROTECTED] changed:
What|Removed |Added
CC||
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
--- Additional Comments From [EMAIL PROTECTED] 2002-10-23 03:42 ---
Created an attachment (id=3572)
TAR archive with diff's and th
gzilla/show_bug.cgi?id=13866
[PATCH] Support for CCITT encoding of TIFF images in PDF output
Summary: [PATCH] Support for CCITT encoding of TIFF images in PDF
output
Product: Fop
Version: 0.20.4
Platform: Other
OS/Version:
[mailto:dev.jeremias@;greenmail.ch]
Sent: Tuesday, 13 August 2002 12:54
To: [EMAIL PROTECTED]
Subject: Re: Encoding Filters(Formally Re: Hope this helps-
RunLengthEncod eFilter)
Manuel
Looks like I missed this. At least, I can say that I could profit from
CCITT group 4 because we have a project at w
Hiloliddin Karimov wrote:
> When I try serialize PDF, that has cyrillic characters I get .
You have to install and use a font which contains
glyphs for the cyrillic characters. Most unicode
fonts will do, for example Arial from Win2K/XP
Font installation instructions can be found somewhere
i
Hi All,
Is possible to show the
international (cyrillic)
letters in PDF by use FOPSerializer.
When I try serialize PDF,
that has cyrillic characters
I get .
Is there some encoding:
<map:serializer name="html"
mime-type=&q
Manuel
Looks like I missed this. At least, I can say that I could profit from
CCITT group 4 because we have a project at work where we have to include
several different monochrome images in a lot of documents. So this may
decrease file size when compared to the FlateEncodeFilter. If it's
dependen
into the CCITT filter briefly and noticed at that time
> the JAI API has this and many other encoding filters in it. When trying to
> see how much work it would have been to integrate the JAI into the FOP I
> noticed the FopImageFactory has some commented out code that would lead me
> to
Tuesday, 13 August 2002 10:41
To: [EMAIL PROTECTED]
Subject: Encoding Filters(Formally Re: Hope this helps-
RunLengthEncodeFilter)
Jeremias
I would love to have some fun, but is this your idea of fun?? ;-)
I will take you up on the offer, report back and tell you whether it was
found to be fu
Jeremias
I would love to have some fun, but is this your idea of fun?? ;-)
I will take you up on the offer, report back and tell you whether it was
found to be fun or not.
Also, I had looked into the CCITT filter briefly and noticed at that time
the JAI API has this and many other encoding
gzilla/show_bug.cgi?id=10043
Encoding when Render to TEXT
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Reso
J.Pietschmann schrieb:
> Oleg Tkachenko wrote:
>
>> Well, encoding-related code looks fine for me, but I cannot build fop
>> in cvs due to Hashtable/HashMap changes:
>
> Oops, didn't clean the build directory before the test build.
> It should be fixed now.
Oleg Tkachenko wrote:
> Well, encoding-related code looks fine for me, but I cannot build fop in
> cvs due to Hashtable/HashMap changes:
Oops, didn't clean the build directory before the test build.
It should be fixed now.
J.
J.Pietschmann wrote:
> Ok, commited to the maintenance branch. I added usage
> info and moved the check for a valid encoding somewhere
> else and provided a warning in case the encoding is
> invalid. PPlease test.
Well, encoding-related code looks fine for me, but I cannot build fop
Oleg Tkachenko wrote:
> As Torsten Straube pointed out that would be nice to have a possibility
> to set TXTRenderer output encoding. I like the idea and here is my
> proposed patch.
Ok, commited to the maintenance branch. I added usage
info and moved the check for a valid encoding
Hello!
As Torsten Straube pointed out that would be nice to have a possibility
to set TXTRenderer output encoding. I like the idea and here is my
proposed patch. I have added new TXTRenderer option "txt.encoding",
which could be set either from command line:
fop.bat d:\table
Torsten Straube wrote:
> While the PDF files are ok, the text files are always UTF-8 encoded.
...
> My FO files always contain an encoding attribute in the XML declaration
> so I thought the ContentHandler might instruct the renderer which encoding
> to use but the SAXContentHandler
to an OutputStram
and this TXTStream assumes a UTF-8 encoding:
public void add(String str) {
if (!doOutput)
return;
try {
byte buff[] = str.getBytes("UTF-8");
out.write(buff);
} catch (IOException e) {
- Original Message -
From: "J.Pietschmann" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 09, 2002 9:58 PM
Subject: Re: Character Encoding
> Holger Prause wrote:
> > I use the character squence − in a html page it will be dispalyed
as
t;
> generated pdf it will displayed as an # sign(which stands for undefined ?)
This means the selected font does not have a glyph for it.
> What can i do to display this character squence, changeing the encoding in
> the stylesheet(or using )?
The only way is to get a font with a glyph
this character squence, changeing the encoding in
the stylesheet(or using )?
Thank you very much,
Holger
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
gzilla/show_bug.cgi?id=10043
Encoding when Render to TEXT
[EMAIL PROTECTED] changed:
What|Removed |Added
Status|NEW |AS
I encountered a problem with embedding fonts with the command prompt like
this...
( java org.apache.fop.fonts.apps.TTFReader C:\myfonts\arial.ttf arial.xml)
Why is it that it always has this Encoding Type H ?
The encoding really ruins the printing format and the line spacing in
Acrobat Reader
[EMAIL PROTECTED] schrieb:
> I've had a couple folks ask me for the modified code so the proper character
> encoding is returned on the toString().getBytes()
> is US-ASCII. This is cool that other people besides me need this.
[..]
> I downloaded this snapshot xml-fop_200205151
I've had a couple folks ask me for the modified code so the proper character
encoding is returned on the toString().getBytes()
is US-ASCII. This is cool that other people besides me need this.
I downloaded this snapshot xml-fop_20020515162132 and I don't see any
modification to the cod
http://www.w3schools.com/xml/xml_elements.asp
Carlos Daniel Schafer wrote:
> Hi
>
> Hello, people
>
> I have a problem with the Font i2of5.ttf when I generated a file PDF
> I can transformed a file XML with a file XSL:FO but I need uses in XML this
> encoding="UTF-8
Hi
Hello, people
I have a problem with the Font i2of5.ttf when I generated a file PDF
I can transformed a file XML with a file XSL:FO but I need uses in XML this
encoding="UTF-8" OR encoding ="ISO-8859-1".
I looked in the Server this next messages errors:
SystemId Unknow
Hi all,
just in case someone hasn't noticed yet ;-)
FOP 0.20.3 is finally available at http://xml.apache.org/dist/fop
for downloading.
The main reason for this release is the conformance to the XSL-FO
Version 1.0 W3C Recommendation. Other changes include:
- support for CMYK and embedded ICC p
[EMAIL PROTECTED] wrote
> I'm beginner in FOP. I have a problem with windows-1250 encoding, please help
> me. My source XML documents looks like this:
[...]
> I use xsl-fo document to transform source document to plain text:
>
>
> http://www.w3
Hi,
I'm beginner in FOP. I have a problem with windows-1250 encoding, please help
me. My source XML documents looks like this:
7 3 4 12 15 16 122
2613233761
...
...
I use xsl-fo document to transform source document to plain text:
http://www.w3.org/1999/XSL/Tran
When I embed a font with FOP on my local maching (NT 4.0) Acrobat says the
font Encoding is "Windows". If I use the Adobe tool to embed the font the
Encoding type is "Built-in". The PDF with Encoding type "Built-in" prints
correctly from our Linux boxes without any
Date: Wed, 21 Nov 2001 14:28:10 + (GMT+00:00)
From: Kristian <[EMAIL PROTECTED]>
To: Alex McLintock <[EMAIL PROTECTED]>
Subject: [FAQ] Encoding
:
:
:
Does FOP support windows-1250 encoding?
-
To unsubsc
Hi,
For your information:
I had a problem with the Sample OCR-B fonts supplied
by IDautomation.com. This font has a Windows Symbol
encoding (PID=3, EID=0) which caused the TTFReader to
say:
Unicode cmap table not present
As a solution I remapped the Symbol encoding to ANSI
encoding which is
be in the resulting pdf file independent from the character
encoding of
the content: 0x3c 0x41 0x3e.
In FOP this pdf tags are handled like normal strings and character
conversion takes place,
which is on ASCII or Unicode or UTF or.. Systems no problem, because
all used character
Title: WinANSI encoding
I have a Java class that takes FO input as a string and returns PDF bytecode as a string. Here's a snippet of my code:
ByteArrayOutputStream buffout = new ByteArrayOutputStream();
driver.buildFOTree(createP
> hello,
>
> i'm a beginner in xml and xsl-fo. i've seen the FAQ and found that FOP
> does not support certain encoding. can anybody here explain what these
> encodings are: windows-1252, ISO-8859-1, UTF-8, UTF-16. and does that
ISO-8859-1 is basicaly encoding for
hello,
i'm a beginner in xml and xsl-fo. i've seen the FAQ and found that FOP
does not support certain encoding. can anybody here explain what these
encodings are: windows-1252, ISO-8859-1, UTF-8, UTF-16. and does that
mean the XSL stylesheet has to make explicit the encoding i
67 matches
Mail list logo
