From: David A. <da...@bo...> - 2003-06-23 14:06:21
|
eng...@ss... writes: >> > except from >> > >> > 1. block justification >> > 2. typewriter fonts are not set correct >> >> What do you mean by that > > in latex it works after the change (your patch) except from 1. 2. no, "what do you mean by #2?" >> > 3. but not the hyphenation >> >> I don't understand what #3 is supposed to mean. > > in latex it works except from 1. 2. but 3. hyphenation is not > supposed to work and does not. means hyphenation is done correct by > latex. > >> That's a shame; LaTeX should try harder ;-) > > try harder to hyphenate unhyphenable words, maybe we should only pass > -try-harder to latex and then go for a beer or 10 :-) After 10 beers I'd probably be satisfied with any formatting at all. >> > in our case fix the rst input, as you did in the rst input. >> > i must rephrase: your rst input has two different page width >> > which is not trivial to handle on paper. >> >> That's one way to look at it. I think it's a little strange to say >> that RST input has a "page width", but maybe David G will disagree. > > i disagree first because, reST documents are documents on their own > without processing needed, and therefore have a width (sometimes two > width :-). OK. >> > * e.g. ams defines a lot of ```\hyphenation{}``s at the start of it's >> > class file. >> >> Don't know what ams is, and I don't know what ``\hyphenation{}`` does. > > ams is the american mathematicl society, which did their own latex version. > with \hyphenation{an-oth-er or-longer and-morewords} one can specify hyphenation > rules. Oh, that sounds useful. >> > * you donot want to hyphenate variablenames elsewhere. >> >> That's mostly true, at least, I want to avoid it with extreme >> prejudice. > > does not make it easier. Understood. Probably adding spaces within <...> is the best policy option we have. >> >> >> Get TeX to do something smarter for us? >> >> > >> >> > if the problem is due to unbreakable long texts, this might be hard. >> >> >> >> That's sad, I guess. I know a little about the mechanisms in TeX >> >> that choose line breaks, and if they can't handle this it's just an >> >> unfortunate lack of parameterizability. > > parameterizability is there just delve into the class files > (actually they are literate documents). Heh, you mean hack the 'C' source code, right? >> > 1. hyphenation for code (typewriter font): >> > >> > 0. typewriter font width is not handled correct. >> > 1. latex does not do it, there might be some reason >> > 2. it might be possible, but then it would be done >> > in all the document not only in the tables. >> > 3. no hyphen when hyphenating code, but a hyphen >> > when not hyphenating code: impossible (maybe) >> > >> > 2. block justification in tables is not always pretty >> > (unbearable in fact). >> >> Probably it would look better if I stopped using \lazy. > > no continue as you are (man getting real deep :-) I don't get what this means, sorry. My funnybone is on the fritz. > actually i real donot think it will improve, but try it. Probably true. >> > 3. pagenumber location top,bottom, ... twoside >> > >> > see gschwandts docfactory AFAIR he uses fancyhdr for this. >> > >> > you could see for 3. and for 4. and 5. if you can find em. >> >> > >> What are 4. and 5. ? > > that is what i asked you ? Even more confused now... > cheers without promises i have look for 2. and sweep over 1. ...and a little more still, but I think I get your meaning. -- Dave Abrahams Boost Consulting www.boost-consulting.com |