Hi Phil
I'm not sure. I'd have to do dive deeper into this. Could be tricky, too.
Maybe someone else has already looked into this. I know it's an issue
for a number of users.
On 30.08.2010 17:22:02 bonekrusher wrote:
>
> Hi Jeremias,
>
> Thanks for following up. In your opinion, how hard would
Hi Trevor
There's currently no way to avoid this. FOP paints each border segment
separately. To avoid artifacts like that we'd have to add functionality
that tries to combine border segments as much as possible but that's
very difficult, especially since we've started to support all border
styles
>
> you need an xsl as well...
>
the xml with Nikos does not knwo which font to use:
> my xsl contains explicit calls to the xml:
>
This is exactly the reason it didn't work. Thank you Spyros!
I edited name2fo.xsl. It was:
Hello, !
and i changed it to:
Hello, !
So
Hi Jeremias
I am using Adobe Reader 9.3.4 and I can see the "Smooth Line Art" option in
the preferences, but it is always greyed out (and checked!). It seems to be
a forced setting regardless of the "Smooth text" setting: none, monitor, or
laptop/LCD. None of these alternatives seem to make any di
Trevor, try turning off "Smooth Line Art" in Acrobat Reader (Preferences,
Page Display). If the effects go away, you'll know that it's
anti-aliasing that causes this. I'll bet it's that but we can't do much
about it. Won't happen in print. HTH
On 30.08.2010 21:05:15 Trevor Nicholls wrote:
> Hi
>
Sorry, I omitted to say this is with FOP 0.95 on Fedora Linux.
Cheers
T
-Original Message-
From: Trevor Nicholls [mailto:tre...@castingthevoid.com]
Sent: Tuesday, 31 August 2010 7:05 a.m.
To: fop-users@xmlgraphics.apache.org
Subject: edge effects with consecutive colored blocks
Hi
Wher
try the following:
1. rewrite your fop conf file to read as follows:
...
...
2. rm ~/.fop/fop-fonts.cache
then rerun to see if you get different behavior;
the two changes above ensure that FOP has access to the system supplied
fonts (via auto-detect), a
Hi
Where my input XML contains "fragment" elements I am generating fo:blocks
with a grey background and black border. Consecutive fragments are coalesced
into what looks like a single block with one outer border (but they need to
be separate fo:blocks so that page breaks occur at a block boundary)
Here is my command that works [fop 0.95!]:
SJPMac2:fop095$> ./fop -xml list.xml -xsl printPDF.xsl -c ./conf095/fop.xconf
-pdf printList.pdf
you need an xsl as well...
the xml with Nikos does not knwo which font to use:
my xsl contains explicit calls to the xml:
...xsl snippet:
Symbol has no tonos whatsoever, FOP will always replace the unfound character
with #.
Symbol has only {ΑΒΓΔ.. Ω, αβγφ.. ω} this makes 48 Greek characters total.
You have to use a font like Arial.ttf that includes the complete 128 greek
glyphs.
Spyros Papantoniou, PhD
On 30 Αυγ 2010, at 7:37
How does your xsl look like?
It works for me though...
this is how I call the Arial fonts and it works:
ΕδφΑ1: Αναφορά Πρωτοκόλλου μεταξύ .. και ..
Unfortunately FOP insists to put a "#" in place of "ί".
I can confirm that Arial.ttf contains a CMAP entry for all the required
characters. I opened Arial.ttf with Character Map (the Windows utility for
viewing fonts). There I inserted code "03af" and it showed the character
"ί".
The same applies
Thanks Jeremias.
Marijan (Mario) Madunic
Publishing Specialist
New Flyer Industries
-Original Message-
From: Jeremias Maerki [mailto:d...@jeremias-maerki.ch]
Sent: Monday, August 30, 2010 9:59 AM
To: fop-users@xmlgraphics.apache.org
Subject: Re: Configuring 1.0 Fonts (PDF rendering)
Bas
Our web designer says the Adobe font viewer product is showing that character
in that font.
If the character is not in the font, what happened to the message in the
console about not finding the glyph?
From: Pascal Sancho [mailto:pascal.san...@takoma.fr]
Sent:
Hi,
On my WinXP, the LTYPE.TTF (AKA "Lucida Sans Typewriter") doesn't
contain the glyph for \u25A1.
You should try another font.
--
Pascal
Le 18/08/2010 21:04, Eric Douglas a écrit :
>
> I'm trying to print a character to a PDF as □ which is supposed
> to be a square and it's printing a # characte
Special font characters are broken in FOP 1.0.
In 0.95 I referenced a unicode character which was not in my custom font and
got a message in my Java Console about glyph not found.
I changed it to a unicode character which is in the font and I get that
character with 0.95. That same code in 1.0 i
Hi,
'#' indicates that the glyph is not available in any font used by FOP.
Note that SVG uses the fonts installed in the system, while FOP needs
that used fonts are set in config file (if you use a non standard font).
So, you have to ensure that the fonts used in SVG are both declared in
your syst
Hi Jeremias,
Thanks for following up. In your opinion, how hard would it be to either
create an extension (like what was used in 20.5) or implementing it in the
next release?
Thanks,
Phil
Jeremias Maerki-2 wrote:
>
> The hard truth is that someone has to implement table markers to achieve
>
Two possibilities:
1. Use XSLT with its document() function.
http://www.w3.org/TR/xslt#document
2. If you have an XInclude-capable XML parser (or a SAX filter for
XInclude), you can use XInclude.
http://en.wikipedia.org/wiki/XInclude
http://www.w3.org/TR/xinclude/
HTH
On 27.08.2010 21:54:16 S
Basically, you can leave everything as it is except remove the
"metrics-url" attribute from the tag. The is
probably still necessary to make sure the name "Helvetica" is redirected
to your embedded font instead of the implicit base 14 font.
http://xmlgraphics.apache.org/fop/latest/fonts.html#reg
Not sure, but I think you look for fo:marker and fo:retrieve-marker.
There are examples for its usage in FOP's examples/fo/markers directory.
And on the web there should be various tutorials covering the feature.
HTH
On 25.08.2010 17:58:17 twfurst wrote:
>
> I have been working on building a man
The hard truth is that someone has to implement table markers to achieve
that. And that's going to be tricky which is mostly the reason why it
hasn't been done, yet.
On 27.08.2010 19:31:44 bonekrusher wrote:
>
> Hi List,
>
> Can anyone provide some guidance on this issue?
>
> Thanks,
>
>
> bo
FOP doesn't have such an option. The PDF 1.4 spec says in chapter 6.2.1:
"A gray level is equivalent to an RGB value with all three components
the same."
And therefore we render gray values in the DeviceGray color space. That
this doesn't work in your case is a bit surprising. But I've heard
somet
Examples can be found in the docs and the FOP distribution:
http://xmlgraphics.apache.org/fop/latest/embedding.html#examples
HTH
On 23.08.2010 11:05:38 Alexander Orlov wrote:
> Is there a "best practice" to generate PDFs out of Java Beans. Any hints are
> appreciated :)
>
> Cheers
> Alex
Jer
FOP uses Java object serialization for the font cache. And the
serialVersionUID can change when the layout of that file changes (from
FOP version to FOP version) in which case FOP cannot read the font cache
file. It then just builds a new one. You're absolutely safe to ignore
that warning.
On 20.0
Hi,
This is how I am using FOP to process XSL.FO into PDF. I agree that
the issue is to do with too much of memory consumption. Is there a better
way to process this large FO file into PDF using FOP?
String xml = builder.getReport(); /// gets the XSL:FO file data approx 50mb
PdfStorage pdfHolder
You're seeing the effect of "indent inheritance":
http://wiki.apache.org/xmlgraphics-fop/IndentInheritance
Yes, FOP's behaviour is correct with respect to the specification. Yes,
it's unexpected.
You have two options:
1. Enclose the contents of the block-container with an fo:block where
you set
I don't actually use borders around what I draw in the block tag.
I sort of cheat. I use absolute positioning for everything. Since I
already know exactly where every block-container is going, I draw lines
around block objects using a different block within a different
block-container. For a box
On 30.8.2010 14:15, Eric Douglas wrote:
I don't know if it would help but I split that up. I use padding-top,
padding-bottom, padding-left, padding-right.
Thanks for the tip, but I still have the same problem. Tried randomly
attributes I suspected (border-separation, border-spacing, break-bef
I'm using the reference-orientation=90 as a workaround until I get time
to test to get the other way to work.
The 90 reference prints fine. It just doesn't look right. If I load it
into preview or PDF it's just portrait turned sideways, so they have to
turn their head or their screen to read it.
I don't know if it would help but I split that up. I use padding-top,
padding-bottom, padding-left, padding-right.
I don't know how the borders would look since I never draw anything from
the block-container, and I tell it where to put all my output with
position="absolute", so if I want a border
Hi,
I have very simple example where I nest block inside block-container. I
set both paddings and margins to 0. I am confused since unexplained
padding (left and right) appears inside block-container.
I would expect that borders are one next to another but this is not the
case. Top and botto
Dont use Symbol!
Its a mess it has only the 24 Greek letters not accents, not dialysis...
Find a font that has full UTF-8 glyph set in Greek,
like on the Mac Arial, Times New Roman, Helvetica all have it.
I dont have Windoze to check which fonts have the full glyph set.
FreeSans I discovered is
33 matches
Mail list logo
