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 -style output) before doing another release. -Peter-
Re: Building fop and batik
The Commons module is not yet a prerequisite to build FOP but will be in a few minutes. But there will be a xmlgraphics-commons.jar in FOP's lib directory. OTOH, you will want to look at the sources of Commons because that's where the stuff interesting for your Folio will eventually end up. Maybe it might be a good idea to have repository commit messages for xmlgraphics-commons sent to fop-dev (and batik-dev)? -Peter-
Re: Hyphenation
"Luca Furini" <[EMAIL PROTECTED]> wrote: Manuel Mall wrote: Not sure what other committers and the PMC think but as a vote on the release has started I would suggest no further changes to the codebase unless agreed? What I am saying is - by all means do the development but don't put it back into svn until after the release. Ok, this seems a good idea. Speaking as a kibitzing non-committer... Branching in subversion is easy, and very cheap. It would make sense to branch 0.90 from trunk now, and allow development on trunk to continue freely. (Alternatively, you could freeze trunk and do the development on a branch, but branching the release probably makes more sense.) -Peter-
Re: zero width space
On Fri, 2005-11-04 at 11:55 +0800, Manuel Mall wrote: > On Fri, 4 Nov 2005 04:46 am, J.Pietschmann wrote: > > Manuel Mall wrote: > > > With respect to U+200B it says in > > > > [snip] > > > > > It therefore surprises me that you imply U+200B may expand in > > > justification. > > > > The Unicode 3.0 book explicitely mentions that ZWS may be expanded > > for justification, to my great surprise. The 2.0 book doesn't have > > any remarks in this direction. I don't have access to a book more > > recent than 3.0. Maybe they changed mind (again...). > > > Any one out there who has the 4.0 book and can shed some light on this? It says that U+200B normally has no effect on letter spacing in most scripts, but only indicates a word boundary (and therefore a possible line break). It also mentions that when letter-spacing Thai it may grow to have a non-zero width, but that is the exception. (Thai apparently doesn't put spaces between words, and uses U+200B as a word separator.) -- Peter S. Housel <[EMAIL PROTECTED]>
Re: Maintainability
"Peter B. West" <[EMAIL PROTECTED]> wrote: Simon Pepping wrote: Maintaining FOP means maintaining a digital typesetting system means maintaining some of the best digital typography algorithms. I plan to resume my documenting activities in the coming months. I look forward to the challenge to document Knuth's algorithms and FOP's implementation of them in a clear and widely understandable fashion. That's a good thing, Simon, and your documentation is very comprehensive. However, I think the question still deserves serious consideration. You seem to be saying that inferior algorithms should be used for the sake of developers who don't have time to read the internals documentation. That doesn't seem like a worthwhile trade-off to me. -Peter-
Re: Let's write the release plan for the first preview release
On Wed, 2005-08-31 at 10:07 +0200, Jeremias Maerki wrote: > Like others I'm hesitant to call it 1.0 just yet. 0.9 sends the right > signal IMO. We're not quite where we want to be but we are soon and > people can start looking at the new package. I would recommend calling it 0.90, since obviously 9 < 20 which may confuse packagers and package management systems. -- Peter S. Housel <[EMAIL PROTECTED]>
