World: r3wp

i'm going to play with the penalties and demerits for hypens to see 
if i can get a better output; however the columns in the test are 
pretty small so it's hard to get a good ouput anyway.

hyphenation dictionaries use small tables of characters to decide 
where to put the hyphens

also notice that the columns have a different width (i think TeX 
can't do this, not easily at least)

I noticed that.

i think TeX has a very good hypenation algorithm (at least it was 
the best at the time)

Yes, I'm using it

yet it's something for higher level dialects to do imho. i.e. makedoc 
would do that.

Not sure .. I think I would want to see it at the pdf-maker level

that means the pdf maker has to be aware of the language of any paragraph 
(or part of paragraph) and so on.

localised versions :)

imagine you want to typeset a sentence in english that quotes a sentence 
in italian...

or, if i ever get to support unicode, a sentence in english that 
quotes japanese.

i want this to stay at a upper layer. :) i will have to do it anyway 
- i'll have to do the pdf emitter for qml for e.g.

(and surely the md3 one)

winansiencoding does not have ligatures - too bad, so that'll need 
to wait for when i get to unicode. :(

anyone interested in writing the user documentation for the pdf maker 
2?

sure, but it would require that I know something about pdf maker 
2, wouldn't it? :-)

do you want it to be based on the PDF Maker 1 docs?

but what will we use ?

:)

Gabriele, it's pretty cool. Good reference, too.
Does underline not work yet ?

First thing I tried of course was bold, italic and underline. Sorry, 
I'll try to stick to positive comments.

henrik, you can know by reading the developer docs. but you will 
also make examples and explain it so that knowledge of the internals 
of pdfmaker is not necessary :)

e.g. http://www.colellachiara.com/soft/PDFM2/pdf-maker.html#section-3
gives a description of the dialect that you can base the user docs 
on.

e.g. (above url) gives a description of the dialect that you can 
base the user docs on. (text was not visible in previous post)

Anton, only a few things of the text dialect are implemented. i wanted 
to get to a working version as soon as possible so that i could test 
the typesetter easily.

iirc underline is not supported directly by PDF, but the new typesetter 
could probably add that. not high pri right now (although qml will 
need it - actually, it'll need strikethrough)

bold and italic are a different font (i.e. you use Times-Italic instead 
of Times-Roman)

Gabriele,  I want to thank you for such beautifull code prentation. 
Did you release the Litterate programming tool you use for this? 
Where do I look? Thanks

not yet, there are still parts of it that are very far from complete. 
i can release the version i'm using to those brave enough to try 
it out, but i think you really need to be brave. :)

the only publicly released part for now is the emitter: http://www.colellachiara.com/soft/MD3/emitters/wetan.html

anyway, i'm glad you like the presentation :) if you spot any typos, 
or find parts that are not clearly explained etc. (aside from the 
still missing parts), please let me know. the better that gets, the 
more people can work on it, fix bugs, add new features and so on 
 :)

gabriele, I noticed in Safari that the dialect specs page you posted, 
the table of contents and the disclaimer is layered on top of each 
other.

http://hmkdesign.dk/layoutbug.png

ok understood.

Actually, I am in the wrong group. I was talking about QML-Ed. Sorry!

pdf-maker does layers?

graham, the image is HTML from Safari

Henrik, do you have a fix for the CSS? (actually, i'd need someone 
to create a good CSS for wetan...) I have only tested it on Firefox 
so far.

Anton, ah, well, Reichart doesn't want underline in QML.

only strikethru is there.

I can see the logic and agree with that.  Umm, are you still thinking 
about it or should Underline be removed from the QML-ED reference 
?

ah, right... hmm, well, i think i should remove it from the reference, 
although underline is just commented out from the source. if ever 
reichart decides to add it back, i can readd it to the reference 
:)

ok, good :) one less confusion.

gabriele, looking at the source, I'm not sure it's enough to fix 
the CSS. it would be far easier to manage if the history and the 
license was wrapped in a table with two cells. the page actually 
also breaks when using Firefox and making the window narrow.

henrik, it does not necessarily need to appear that way. i prefer 
a semantic approach in the source. history and license are just two 
fields, how they are displayed depends on the CSS, not on the xhtml 
structure.

gabriele, well, anyway, I think it's not very easy to place up elements 
next to eachother in a controlled way other than by using a table. 
<div>s are nice, but there are limits to how much fiddling should 
be necessary.

then we don't place them next to each other. :)

pdf-maker updated (docs almost finished)

updated again.