headers
Keiron Liddle | 2 Sep 2002 10:52

Re: TTFReader bug

On Sat, 2002-08-31 at 15:35, Jessica P. Hekman wrote:
> I think it's still worth getting TTFReader to read these fonts without 
> having to convert them. Keiron, you said you had a solution; do you have a 
> patch? Do you need any help making one? (I keep offering to help and not 
> actually doing anything; I feel guilty.)

I have committed what I think is the fix (to HEAD) and also added some
logging.
If you could checkout the code and give it a go it would be great.

I also changed it so that it handles fonts without a unicode cmap
better. There is a bug for an error caused by this unsupported format.

Keiron.
Permalink | Reply | 3 comments |
headers
Keiron Liddle | 2 Sep 2002 15:08

[VOTE] development direction


In order to clarify what direction we intend to make for development. We
can have a vote.

So do we:
- make one more release of branch (0.20.5) and then freeze development
there. No new features and only fix critical bugs or compatibility
problems.

- all development on HEAD, get a few more basic things started (tables,
lists, spacing, borders) then make a development release

+1

Keiron.
Permalink | Reply | 11 comments |
headers
Tim Landscheidt | 2 Sep 2002 15:43
Picon

Re: [VOTE] development direction

Keiron Liddle <keiron <at> aftexsw.com> wrote:

> In order to clarify what direction we intend to make for development. We
> can have a vote.

> So do we:
> - make one more release of branch (0.20.5) and then freeze development
> there. No new features and only fix critical bugs or compatibility
> problems.

> - all development on HEAD, get a few more basic things started (tables,
> lists, spacing, borders) then make a development release

Though only a user, I'd like to have an idea how this should
be achieved. Does this mean that FOP volunteers are whipped
to write HEAD code or that patches enhancing functionality
in the maintenance branch are simply rejected?

  From a user's perspective, I find the latter notion rather
discouraging.

Tim
Permalink | Reply | 3 comments |
headers
Keiron Liddle | 2 Sep 2002 16:03

Re: [VOTE] development direction

On Mon, 2002-09-02 at 15:43, Tim Landscheidt wrote:
> Though only a user, I'd like to have an idea how this should
> be achieved. Does this mean that FOP volunteers are whipped
> to write HEAD code or that patches enhancing functionality
> in the maintenance branch are simply rejected?

This means that we focus effort and direction in one place. Then
volunteers know where to direct their effort and work on improving the
project.

>   From a user's perspective, I find the latter notion rather
> discouraging.

From a developers perspective splintering the effort and creating
confusion and duplication is more than discouraging.

> Tim
Permalink | Reply | 0 comments |
headers
Jason Foster | 2 Sep 2002 16:06
Picon
Picon
Favicon

Re: [VOTE] development direction

Speaking as a user, whatever course of action that provides a complete 
reference implementation of XSL:FO (performance be damned!) would be 
preferred.  As I understand the situation, <float> elements cannot be added 
to the current architecture, and as such a move to HEAD would be the way to 
go.

Jason Foster
Permalink | Reply | 1 comment |
headers
Rob Hague | 2 Sep 2002 16:36
Picon
Picon
Favicon

Re: [VOTE] development direction

On Mon, Sep 02, 2002 at 10:06:23AM -0400, Jason Foster wrote:
> Speaking as a user, whatever course of action that provides a complete 
> reference implementation of XSL:FO (performance be damned!) would be 
> preferred.  As I understand the situation, <float> elements cannot be added 
> to the current architecture, and as such a move to HEAD would be the way to 
> go.

I've been wanting to get into FOP development, and have been trolling the
lists for a couple of weeks in order to get a feel for how things are done,
and where I could be useful. <float>s are probably my number one wish as well,
so I would also be in favour of a move to HEAD, but then again I don't have a
running system that relies on having a stable version of FOP to worry about...

--

-- 
Rob Hague

Co-creator of http://www.solipsistworker.org.uk/ImMDB
Researcher at http://www.cl.cam.ac.uk/~rgh22
Lord Protector of http://www.rho.org.uk
Permalink | Reply | 0 comments |
headers
Jessica P. Hekman | 2 Sep 2002 17:58

Re: TTFReader bug

On 2 Sep 2002, Keiron Liddle wrote:

> I have committed what I think is the fix (to HEAD) and also added some
> logging.
> If you could checkout the code and give it a go it would be great.

Done. TTFReader now generates the XML file with no errors for two fonts
which previously gave it trouble!

However, when I tried actually using the generated XML file for one of 
those fonts, the font didn't show up in the PDF output. (The characters in 
that font just weren't there.) I took at look at two XML files:

a) I took a "broken" font, ran it through FontTools (mentioned in this 
thread earlier), and then ran the old version of TTFReader on that. This 
is XML file a. This XML file works (the resulting PDF looks as I expect).

b) XML file b is the new version of TTFReader run on the original, broken 
font. This XML file does not work (the characters in the embedded font in 
the PDF are invisible.)

The beginning of file (a):

<font-metrics

type="TRUETYPE"><font-name>Conga,Normal</font-name><embed/><cap-height>704</cap-height><x-height>589</x-height><ascender>927</ascender><descender>-300</descender><bbox><left>-228</left><bottom>-211</bottom><right>1219</right><top>927</top></bbox><flags>33</flags><stemv>0</stemv><italicangle>0</italicangle><subtype>TRUETYPE</subtype><singlebyte-extras><encoding>WinAnsiEncoding</encoding><first-char>0</first-char><last-char>255</last-char><widths><char 
idx="0" wdt="500"/><char idx="1" wdt="500"/> ...

The beginning of file (b):
(Continue reading)

Permalink | Reply | 2 comments |
headers
Christian Geisert | 2 Sep 2002 19:46
Picon
Favicon

Re: [VOTE] development direction

Keiron Liddle schrieb:
> In order to clarify what direction we intend to make for development. We
> can have a vote.
> 
> So do we:
> - make one more release of branch (0.20.5) and then freeze development
> there. No new features and only fix critical bugs or compatibility
> problems.
> 
> - all development on HEAD, get a few more basic things started (tables,
> lists, spacing, borders) then make a development release

+1

The crux is to get HEAD to produce "usable" output.

Christian
Permalink | Reply | 0 comments |
headers
J.Pietschmann | 2 Sep 2002 21:49
Picon
Favicon

Re: [VOTE] development direction

Keiron Liddle wrote:
> - make one more release of branch (0.20.5) and then freeze development
> there. No new features and only fix critical bugs or compatibility
> problems.

So what is the list of critical problems to fix for 0.20.5?

J.Pietschmann
Permalink | Reply | 4 comments |
headers
J.Pietschmann | 2 Sep 2002 22:34
Picon
Favicon

Re: cvs commit: xml-fop build.xml

chrisg <at> apache.org wrote:
>   +    <style
>   +       in="${Courier.xml}" style="${fontfile.xsl}"
>   +       destdir="${build.src}/${replacestring}/render/pdf/fonts" 
>   +       out="${build.src}/${replacestring}/render/pdf/fonts/Courier.java">

 From the Ant docs (1.4.1 and later):
  destdir: directory in which to store the results.
   required: Yes, unless in and out have been specified.
Seems to be redundant.

BTW should we upgrade the ant.jar distributed
with FOP?

J.Pietschmann
Permalink | Reply | 0 comments |

Gmane