developer toolbox

asciidoc fop patch za 0.95 (detalji na mailing listi)

http://hg.sharesource.org/asciidoc/rev/e1bc93fef523

problem naših slova: postoji kako sam i očekivao problem naših slova kod pdf-a. inače html output uredno prikazuje naša slova.

da li fop-0.90.5 radi posao kako treba ?

testirao sa fop 0.95 ali ne radi

da bi uopšte izgenerisao to patchirao asciidoc source (komentarisao fop.extensions liniju)

sudo vi /etc/asciidoc/docbook-xsl/fo.xsl

<!-- <xsl:param name="fop.extensions" select="1" /> -->

primjetio sam međutim da mi loše formatira slike - ne mogu da stanu na stranicu, dok je fop 0.20.5 fino smanjio sliku tako da stane na stranicu

znači, držimo se fop-a 0.20.5 za pdf generaciju.

što se tiče naših slova ... hmm vječni problem

http://en.wikipedia.org/wiki/ISO_8859-2

asciidoc 8.2.7 w/ dblatex fails to show degree symbol

"super reference internacionalnih slova"http://www.eki.ee/letter/chardata.cgi?lang=lt+Lithuanian&script=latin

ccaron (č): decimal: č UTF-8 (c4, 8d)

hm ovo je do fop-a

test txt

:deg: {amp}#176;
:ccaron: {amp}#269;

test {nbsp} {gt}
test-2 37{deg}
test-3 {ccaron}
kraj --------------------

ovo radi sa html ali pdf generacija daje tarabu na ccaron supsituciji, dok recimo pdf fino kaže 37(znak za stepeni celzijusa)

http://mail-archives.apache.org/mod_mbox/forrest-dev/200311.mbox/%3C3FA90CC8.4000006@isu-gmbh.de%3E

Oliver Vecernik wrote:
> Christian Geisert schrieb:

[..]

>> For the PDF see http://xml.apache.org/fop/faq.html#pdf-characters
>> (it seems c-caron is not part of ISO Latin1)
> 
> I'm no font expert, but as far as I know it is part of ISO Latin2. But 
> I've rendered it already correctly from other programs and if I look at 
> the PDF spec (V1.3) the caron should be at 031 (octal). But it is also 

You need a c-caron, caron is not enough ;-)
And c-caron is not part of the standard PDF fonts. So you need to use 
(and embed) a custom font for the PDF.

> renderd to a `?' in the trail altough it is rendered correctly just the 
> line under the trail. That's why I was asking if this is a bug.

The problem with the trail sounds like a bug (and is very likely not 
related to the PDF problem). How does the html source for the c-caron 
look like?

Christian

List: fop-dev
Subject: Re: Croatian characters in fop created pdf
From: Keiron Liddle <keiron () aftexsw ! com>
Date: 2002-12-13 10:36:21
[Download message RAW]

On Fri, 2002-12-13 at 08:35, Adis Katkic wrote:

Hi,
croatian characters are of type ISO-8859-2 (latin 2)
The unusual characters are: .

Whatever the characters are, all I can see is a "."

I don't know if I said it before, but Fop doesn't use the fonts from you
platform, apart from the default fonts you need to embed the fonts.

Thanks Keiron but I'm still stack with my problem.

If you look at the docs/examples/fo/fonts.fo it has all the
characters for the inbuilt fonts.

If the characters you need are not there then you will need
another font that has the characters, if they are there you need to use
the correct encoding or character reference.

http://xmlgraphics.apache.org/fop/trunk/fonts.html

If you want FOP to use custom fonts, you need to tell it where to find them. This is done in the configuration file and once per renderer (because each output format is a little different). In the basic form, you can either tell FOP to find your operating system fonts or you can specify directories that it will search for support fonts. These fonts will then automatically be registered.

<renderers>
<renderer mime="application/pdf">
<fonts>

<directory>C:\MyFonts1</directory>

         <directory recursive="true">C:\MyFonts2</directory>

         <auto-detect/>  
      </fonts>
   </renderer>
</renderers>

http://www.nabble.com/Problems-with-czech-characters-td2945890.html

....

Hello!

I had same problem due to ISO latin 2 character set that is in use in our country (Slovenia).

You have to create font metric file for font types you want to use (from *.ttf) and register those files with FOP.

You can find instructions on how this is done here: http://xmlgraphics.apache.org/fop/0.20.5/fonts.html#custom

http://xmlgraphics.apache.org/fop/0.94/fonts.html

FOP includes TTFReader, which reads the TTF file and generates an appropriate font metrics file for it.

Use it in a similar manner to PFMReader. For example, to create such a metrics file in Windows from the TrueType font at c:\myfonts\cmr10.ttf:

java -cp build\fop.jar;lib\avalon-framework.jar;lib\commons-logging.jar;lib\commons-io.jar
           org.apache.fop.fonts.apps.TTFReader [options]
             C:\myfonts\cmr10.ttf ttfcm.xml

TTFReader [options]:

    * -d <DEBUG | INFO > Sets the debug level (default is INFO).
    * -fn <fontname> Same as for PFMReader.
    * -ttcname <fontname> If you're reading data from a TrueType Collection (.ttc file) you must specify which font from the collection you will read metrics from. If you read from a .ttc file without this option, the fontnames will be listed for you.
    * -enc ansi Creates a WinAnsi-encoded font metrics file. Without this option, a CID-keyed font metrics file is created. The table below summarizes the differences between these two encoding options as currently used within FOP. Please note that this information only applies to TrueType fonts and TrueType collections: