TeX’s \nonfrenchspacing with CSS?
|
|
Thread rating:  |
Hendrik Maryns - 15 May 2008 11:59 GMT Hi,
Typography rules for English suggest to have a longer space after a full stop than between normal words. TeX does this automatically when the language is English, using funky spacing rules.
Is it possible to do something similar with CSS?
I.e. I’d like
<p>I am currently working on a query tool for linguistic tree banks. The goal is to write a query tool which can handle queries of some formalism stronger than first order logic.</p>
to be rendered with an additional before ‘The’.
TIA, H. - -- Hendrik Maryns http://tcl.sfs.uni-tuebingen.de/~hendrik/ ================== http://aouw.org Ask smart questions, get good answers: http://www.catb.org/~esr/faqs/smart-questions.html
Andreas Prilop - 15 May 2008 15:34 GMT > Typography rules for English suggest to have a longer space > after a full stop than between normal words. I question this. Specifically, to which rules do you refer? Name author, title, year of publication, etc.!
 Signature Solipsists of the world - unite!
Ben Bacarisse - 15 May 2008 17:42 GMT >> Typography rules for English suggest to have a longer space >> after a full stop than between normal words. > > I question this. Specifically, to which rules do you refer? > Name author, title, year of publication, etc.! http://en.wikipedia.org/wiki/French_spacing includes 10 citations (numbers 6 to 15) that might be what you are looking for.
The practise seems to be falling out of favour, so there are no doubt style guides that recommend the same width of space in all cases, but unless the citations in that article are wrong, there have been guides and authorities that support this widely held view.
 Signature Ben.
Jukka K. Korpela - 15 May 2008 21:20 GMT Scripsit Hendrik Maryns:
> -----BEGIN PGP SIGNED MESSAGE----- Don't be ridiculous. This is Usenet.
> Typography rules for English suggest to have a longer space after a > full stop than between normal words. People who claim so can typically cite just their grandmother's typewriting teacher's oral statements.
> Is it possible to do something similar with CSS? No, not the way you want, not at all. There's no selector that could refer to a statement or to a statement-terminating full stop, unless you use explicit markup, typically <span> with class.
> I.e. I'd like > [quoted text clipped - 3 lines] > > to be rendered with an additional before 'The'. So why don't you try putting a no-break space there, in the content? Stay tuned to unexpected effects, though. A no-break space isn't just non-collapsing; it's also a no-break space, whatever that means to each browser.
If you really want the effect you describe, use markup like <span class="full-stop">.</span> for each sentence-terminating full stop (period), with CSS code like .full-stop { padding-right: 0.25em; }
> iD8DBQFILBeNe+7xMGD3itQRAmPIAJ9yVf1dttVySqax3gbE1hxZoxoTUACdFSmu > 33HavjkUxxXSblL/hHevNIA= > =vHiQ Someone puked on your message, it seems.
 Signature Jukka K. Korpela ("Yucca") http://www.cs.tut.fi/~jkorpela/
Ben C - 15 May 2008 22:05 GMT > Scripsit Hendrik Maryns: [...]
>> Typography rules for English suggest to have a longer space after a >> full stop than between normal words. [...]
>> <p>I am currently working on a query tool for linguistic tree banks. >> The goal is to write a query tool which can handle queries of some [quoted text clipped - 11 lines] > for each sentence-terminating full stop (period), with CSS code like > .full-stop { padding-right: 0.25em; } A neater way of doing it might be to surround each sentence with <span class="sentence">...</span>.
Then use
.sentence { padding-right: 0.25em } .sentence:after { content: "." }
Or not bother with the :after (which is unsupported in IE probably, and a bit silly here anyway) and just type the .s in.
Hendrik Maryns - 16 May 2008 09:44 GMT Ben C schreef:
>> Scripsit Hendrik Maryns: > [...] [quoted text clipped - 26 lines] > Or not bother with the :after (which is unsupported in IE probably, and > a bit silly here anyway) and just type the .s in. Thank you both for your answers. It is as I feared, too convoluted to be practical.
Oh, and yes, Jukka, I disabled PGP for all c.i.w.a.* groups, just for you. I do not think it is ridiculous, but do not want to lose your valuable contributions. See http://mindprod.com/project/mailreadernewsreader.html for some thoughts on signing posts, to which I mostly agree.
H.
 Signature Hendrik Maryns http://tcl.sfs.uni-tuebingen.de/~hendrik/ ================== http://aouw.org Ask smart questions, get good answers: http://www.catb.org/~esr/faqs/smart-questions.html
Jukka K. Korpela - 16 May 2008 20:39 GMT Scripsit Ben C:
> A neater way of doing it might be to surround each sentence with <span > class="sentence">...</span>. [quoted text clipped - 6 lines] > Or not bother with the :after (which is unsupported in IE probably, > and a bit silly here anyway) and just type the .s in. It would in a sense be more logical to use markup for a sentence rather than a punctuation mark, but on the practical side, which of them would you more probably want to style? (Apart from the extra spacing discussed here; it can be added in either case.) Well, maybe there's no difference.
But it would indeed be a bit silly to omit punctuation from the content and rely on CSS for adding it - even if we don't consider the lack of support. In particular, speech browsers would read the text continuously, with no breaks or change of tone at sentence breaks, since they would see no sentence breaks.
Things would be different if HTML had <sentence> markup from the beginning, with due browser support even when CSS is off. But that happened in a parallel universe only.
 Signature Jukka K. Korpela ("Yucca") http://www.cs.tut.fi/~jkorpela/
dorayme - 16 May 2008 10:31 GMT > Typography rules for English suggest to have a longer space after a full > stop than between normal words. TeX does this automatically when the [quoted text clipped - 9 lines] > > to be rendered with an additional before ‘The’. It is highly unlikely to have a benefit over cost to implement and to be always worrying about this in the future.
 Signature dorayme
Jeremy - 17 May 2008 01:31 GMT > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 [quoted text clipped - 6 lines] > > Is it possible to do something similar with CSS? Not with CSS. You could devise some ECMAScript which (for supporting UAs) would replace the sequence /\.\s+/ (full stop followed by some whitespace) with ".\u2003" (full stop followed by em space) in all text nodes. Or you could do this server-side, or even in your original content. I doubt anyone would notice your effort, though.
I also compulsively put a double space after a full stop, and in the early days of using HTML I was quite frustrated by my double spaces being collapsed. Everyone is so used to it by now that the extra space might even look strange in the context of an HTML document.
Jeremy
Johannes Koch - 17 May 2008 03:47 GMT Jeremy schrieb:
> You could devise some ECMAScript which (for supporting > UAs) would replace the sequence /\.\s+/ (full stop followed by some > whitespace) with ".\u2003" (full stop followed by em space) in all text > nodes. Note that not every "." followed by whitespace marks the end of a sentence (e.g. <- abbreviations).
 Signature Johannes Koch In te domine speravi; non confundar in aeternum. (Te Deum, 4th cent.)
Gary Peek - 20 May 2008 22:00 GMT > Typography rules for English suggest to have a longer space after a full > stop than between normal words. I have found that a number of people believe that, but I have never found out why, so... reference, please?
Gary Peek, Industrologic, Inc.
Bert Byfield - 21 May 2008 01:06 GMT >> Typography rules for English suggest to have a longer space after a full >> stop than between normal words.
> I have found that a number of people believe that, but I > have never found out why, so... reference, please? In the typewriter era, the standard business practice was ALWAYS two spaces after a period. Only with the introduction of computers with proportional space fonts did this standard give way, and it didn't go down without a fight from the traditionalists.
Ben Bacarisse - 21 May 2008 03:51 GMT >>> Typography rules for English suggest to have a longer space after a full >>> stop than between normal words. [quoted text clipped - 6 lines] > space fonts did this standard give way, and it didn't go down without a > fight from the traditionalists. But note: it did not come from typewriting[1]. At least three times the inter-word space was the norm in well-set type which became the two-space rule in typescript.
Also, as I have posted elsewhere, it survived well into the computer era.
[1] If the influence was the other way round, one would have explain why the double space from typewriting became the recommended *triple* space in type-set text.
 Signature Ben.
Ben C - 21 May 2008 08:33 GMT >>> Typography rules for English suggest to have a longer space after a full >>> stop than between normal words. [quoted text clipped - 6 lines] > space fonts did this standard give way, and it didn't go down without a > fight from the traditionalists. Use one space normally but two or three after weighty or important sentences. To give them time to sink in.
dorayme - 21 May 2008 09:38 GMT > >>> Typography rules for English suggest to have a longer space after a full > >>> stop than between normal words. [quoted text clipped - 9 lines] > Use one space normally but two or three after weighty or important > sentences. To give them time to sink in. The corollary being that in a sly argument, make absolutely certain there is no double space. Which brings up the important question, is there a CSS way to reduce the space to slightly less than a normal space after *some* full stops?
 Signature dorayme
Ben C - 21 May 2008 12:28 GMT [...]
> The corollary being that in a sly argument, make absolutely certain > there is no double space. Which brings up the important question, is > there a CSS way to reduce the space to slightly less than a normal space > after *some* full stops? You can use a negative margin.
.bogus { margin-right: -0.25em; }
<span class="bogus">Down with this sort of thing.</span> On a related note...
Another useful (but much harder) trick which could do with CSS support is to arrange for the most sly parts of a contract or list of terms and conditions to be at the edges of the page rather than down the middle. This is because speed-reading courses teach you to read a column down the middle.
dorayme - 22 May 2008 00:25 GMT > [...] > > The corollary being that in a sly argument, make absolutely certain [quoted text clipped - 14 lines] > This is because speed-reading courses teach you to read a column down > the middle. <g>
 Signature dorayme
Dr J R Stockton - 22 May 2008 16:53 GMT In comp.infosystems.www.authoring.stylesheets message <Xns9AA4CC6A01E51B ertByfieldCaravela1@66.250.146.128>, Wed, 21 May 2008 00:06:30, Bert Byfield <BertByfield@nospam.not> posted:
>>> Typography rules for English suggest to have a longer space after a full >>> stop than between normal words. [quoted text clipped - 6 lines] >space fonts did this standard give way, and it didn't go down without a >fight from the traditionalists. Recently so. Earlier, I believe that three spaces between sentences was common, with two spaces after a colon and one after a comma.
With a proportional font such as Times New Roman, with its rather feeble and narrow full stop, it's often not as easy as it should be to see when a sentence ends, especially when the topic is such that upper-case letters often appear at the start of words that do not start a sentence.
A decimal point should be at the lower middle of a digit-width space, and at least as wide as the thicker uprights; a sentence-terminating full stop should be of similar size, but to the left of an en- or em- space; an indicator of abbreviation should be horizontally-centred in a thin space. Manual composition could easily handle that; it's harder nowadays.
 Signature (c) John Stockton, nr London UK. ?@merlyn.demon.co.uk DOS 3.3 6.20 ; WinXP. Web <URL:http://www.merlyn.demon.co.uk/> - FAQqish topics, acronyms & links. PAS EXE TXT ZIP via <URL:http://www.merlyn.demon.co.uk/programs/00index.htm> My DOS <URL:http://www.merlyn.demon.co.uk/batfiles.htm> - also batprogs.htm.
Ben Bacarisse - 21 May 2008 03:41 GMT >> Typography rules for English suggest to have a longer space after a full >> stop than between normal words. > > I have found that a number of people believe that, but I > have never found out why, so... reference, please? I wrote up a message about this and then just left it since I did not think there were any real matters of fact in dispute -- while there were some rather dismissive remarks, no one actually said that there had never been any authority to support this view.
Note that I used the past tense. I don't think any current authority supports the practise, but there is no doubt that it was once the norm. For example, the 1911 edition of the Chicago "Manual of Style"[1] has this to say:
A standard line should have a 3-em space between all words not separated by other punctuation points than commas, and after commas; an en-quad after semicolons, and colons followed by a lower-case letter; two 3-em spaces after colons followed by a capital; an em-quad after periods, and exclamation and interrogation points, concluding a sentence.
(a 3-em space is a three-to-an-em space, or 1/3em).
At some point between then and now this changed to the current advice which states that a regular word space is to be used after the punctuation that ends a sentence (reference: current (2008) on-line version of Manual of Style -- subscription only).
That there was a change already afoot, resisted by traditionalists, is evidenced by the only reference to inter-sentence space in the otherwise comprehensive "Correct Composition"[2] by Theodoee Low de Vinne. On page 203 there is a footnote:
Thin spacing is practised by several eminent disciples of the fifteenth-century school of typography, apparently on these grounds: As the early printers made exclusive use of one thin space, we should use the thin space only. It is held that this thin space is wide enough to separate words and even sentences
The em quadrat between sentences and the three-to-em space between words are rated as waste white space, and are a vexation to one who admires the mannerisms of medieval copyists.
The standard rule is only referred to obliquely, it seems to be so wide-spread. The tone is not flattering to these radicals. In another book by de Vinne (which I can't find right now) the rule is again referred too only obliquely by stating that when spaces between words have to be reduced from the normal 1/3em, the em quadrat between sentences can be reduced to an en quadrat.
As early as 1913, in the beautifully printed "Type Spacing" by E R Currier, we read[2]:
The best typographers have already discovered that there is no good reason for following the practice of inserting a full em-quad between sentences. As punctuation the em-quad is really superfluous, since the presence of the period and capital provide sufficient emphasis over the spacing between other words in the line to mark the new sentence.
Although I am sure that a /little/ extra space is used between sentences, even in this text. Judge for yourself at [4].
The practise continued well into the computer era. It was the norm in troff and survived into the Plan 9 version (see section 4.1 in [5]). Of course, TeX does something similar (it uses glue with more stretch between words) to this day. These of course are not authorities -- just places where the traditional rule refuses to die.
I will miss it. I like the look (although the full em-quadrant used in early 20th century books does look huge these days) and I think it particularly lacking on the web, where that little extra space helps with all those ridiculous small fonts people keep suggesting to my browser!
---------------- [1] "Manual of style, a compilation of the typographical rules in force at the University of Chicago press, with specimens of types in use at the University press", University of Chicago Press, Chicago, Ill, 1911.
[2] Theodoee Low de Vinne, "Correct Composition: A Treatise On Spelling Abbreviations, The Compounding And Division Of Words, The Proper Use Of Figures And Numerals, Italic And Capital Letters, Notes, Etc. With Observations On Punctuation And Proof-Reading", Second Edition, New York, The Century Co., 1904
[3] E. R. Currier, "Type Spacing", J. M. Bowles, New York, 1913. [4] Image of page 1 of the above: http://bsb.me.uk/tmp/type-spacing.jpg
[5] B. W. Kernighan, "Troff User's Manual", Plan 9 Ed. (at http://plan9.bell-labs.com/sys/doc/troff.pdf).
 Signature Ben.
Jukka K. Korpela - 21 May 2008 07:01 GMT Scripsit Ben Bacarisse:
>>> Typography rules for English suggest to have a longer space after a >>> full stop than between normal words. [...]
> I don't think any current authority > supports the practise, but there is no doubt that it was once the > norm. Rather, _a_ norm. I think we can say "the norm" only when all relevant authorities agree.
> At some point between then and now this changed to the current advice > which states that a regular word space is to be used after the > punctuation that ends a sentence More exactly, authorities that favored the longer space stopped doing so, _returning_ to the old principles.
> That there was a change already afoot, resisted by traditionalists, is > evidenced by [...] "Traditionalist" is an interesting word: it carries fairly strong connotations, but their sign (positive vs. negative) depends on the expected audience or on the author, depending on the awareness of the author.
Objectively, the longer space practice wasn't really a _tradition_ in the traditional sense, as opposite to the modern sense where anything is a tradition when done second time, and sometimes even when not. Tradition proper is something that has been carried over from human generation to the next, for generations. The practice existed for a few generations only, at most. If it ever was a tradition, it was a short one, and the "traditionalists" that you refer to were actually resisting a return to a much older tradition.
Robert Bringhurst writes, in "The Elements of Typographic Style" (version 3.1; p. 28 - 30):
"In the nineteenth century, which was a dark and inflationary age in typography and type design, many compositors were encouraged to stuff extra space between sentences. Generations of twentieth-century typists were then taught to do the same, by hitting the spacebar twice after every period. Your typoing was well as your typesetting will benefit from unlearning this quaint Victorian habit. As a general rule, no more than a single space is required after a period, a colon on any other mark of punctuation."
> As early as 1913, in the beautifully printed "Type Spacing" by E R > Currier, we read[2]: [quoted text clipped - 5 lines] > sufficient emphasis over the spacing between other words in the line > to mark the new sentence. This is the traditional position, here expressed with a well-formulated rationale for it.
Considering the rationale, it is justifiable to deviate from it at times. Bringhurst adds:
"The rule is sometimes altered, however, when setting classical Latin and Greek, romanized Sanskrit, phonetics or other kinds of texts in which sentences begin with lowercase letters. In the absence of a capital, a full /en space/ (M/2) between sentences may be welcome."
You need to know the rules well _and_ to understand their rationales in order to break them with style.
> Although I am sure that a /little/ extra space is used between > sentences, even in this text. Judge for yourself at [...] > http://bsb.me.uk/tmp/type-spacing.jpg It apparently uses justification that increases or decreases inter-word spacing evenly within a line to make it fit, _except_ that it makes spacing after a period larger than inter-word spacing in general on the same line. This is normal TeX practice too (and we need to take extra measures to prevent in in TeX when it's not desired, e.g. after a period that in fact does not terminate a sentence). It is debatable whether it is good practice, especially if we consider lines where word spacing is very small. Should we afford extra spacing after a period even when it implies that other word spacing becomes even tighter?
There is no way to achieve it directly in CSS, even when using the proposed and partly implemented text-justify property. However, you can simulate it using the trick of inserting a no-break space ( ) after a period that terminates a sentence, before a normal space. This means that the normal space is stretched in justication as any other normal space, whereas the no-break space is, in practice, handled by browsers as a graphic with an empty glyph of fixed width. Demo: http://www.cs.tut.fi/~jkorpela/test/fsp.html
 Signature Jukka K. Korpela ("Yucca") http://www.cs.tut.fi/~jkorpela/
Andreas Prilop - 21 May 2008 09:50 GMT > Subject: =?iso-8859-1?Q?Re:_TeX=E2=3FTs_\nonfrenchspacing_with_CSS=3F?=
| Subject: Re: TeXâ?Ts \nonfrenchspacing with CSS? Prilop's law:
Any non-ASCII character in the Subject line will fail sooner or later (usually sooner).
 Signature Umlaute im Subject sind b?se.
Stanimir Stamenkov - 21 May 2008 16:20 GMT Wed, 21 May 2008 10:50:35 +0200, /Andreas Prilop/:
>> Subject: =?iso-8859-1?Q?Re:_TeX=E2=3FTs_\nonfrenchspacing_with_CSS=3F?= > [quoted text clipped - 4 lines] > Any non-ASCII character in the Subject line will fail > sooner or later (usually sooner). In this case it is because Outlook Express (which Jukka Korpela seems to use) has problem decoding the headers when their encoding is not the same as the one of the message body.
 Signature Stanimir
Hendrik Maryns - 29 May 2008 12:28 GMT Andreas Prilop schreef:
>> Subject: =?iso-8859-1?Q?Re:_TeX=E2=3FTs_\nonfrenchspacing_with_CSS=3F?= > [quoted text clipped - 4 lines] > Any non-ASCII character in the Subject line will fail > sooner or later (usually sooner). I’m an optimist and hope that one day, all the world will be Unicode, even Microsoft’s.
H.
 Signature Hendrik Maryns http://tcl.sfs.uni-tuebingen.de/~hendrik/ ================== http://aouw.org Ask smart questions, get good answers: http://www.catb.org/~esr/faqs/smart-questions.html
Andreas Prilop - 29 May 2008 17:20 GMT > I’m an optimist and hope that one day, all the world will be Unicode, > even Microsoft’s. But one part will be UTF-8, another one UTF-16BE, another one UTF-16LE …
Hendrik Maryns - 30 May 2008 11:27 GMT Andreas Prilop schreef:
>> I’m an optimist and hope that one day, all the world will be Unicode, >> even Microsoft’s. > > But one part will be UTF-8, another one UTF-16BE, another one UTF-16LE … Will it? Almost all Unicode I’ve seen till now is utf-8. It is the default on newer Linuxes already, and on Mac as well, I think. Java uses it. Where is utf-16* used?
H.
 Signature Hendrik Maryns http://tcl.sfs.uni-tuebingen.de/~hendrik/ ================== http://aouw.org Ask smart questions, get good answers: http://www.catb.org/~esr/faqs/smart-questions.html
Michael Wojcik - 30 May 2008 22:56 GMT > Will it? Almost all Unicode I’ve seen till now is utf-8. It is the > default on newer Linuxes already, and on Mac as well, I think. Java > uses it. Where is utf-16* used? In Windows. The original Windows NT 1.0 used UCS-2 as its system character set (with dual APIs for UCS-2 and "Extended ASCII"). These days, Windows uses UTF-16LE as its system character set (still with dual APIs, plus some other provisions for translating among character sets).
 Signature Michael Wojcik Micro Focus Rhetoric & Writing, Michigan State University
Ben Bacarisse - 21 May 2008 19:45 GMT > Scripsit Ben Bacarisse: > [quoted text clipped - 7 lines] > Rather, _a_ norm. I think we can say "the norm" only when all relevant > authorities agree. Very true. There may have been a time, in darkest part of the 19th century, when is was _the_ norm, but I don't know.
<snip>
>> That there was a change already afoot, resisted by traditionalists, is >> evidenced by [...] [quoted text clipped - 12 lines] > was a short one, and the "traditionalists" that you refer to were > actually resisting a return to a much older tradition. I did not mean to imply that there was a tradition of doing it. Maybe I should just have said "resisted by conservatives" instead. The author I quoted comes across as a conservative embattled by falling standards and by new and worrying fads.
<big snip>
> There is no way to achieve it directly in CSS, even when using the > proposed and partly implemented text-justify property. However, you [quoted text clipped - 4 lines] > browsers as a graphic with an empty glyph of fixed width. Demo: > http://www.cs.tut.fi/~jkorpela/test/fsp.html Thank you. Very interesting. For me, the most revealing thing is how bad my browser is at justification. Almost all the spaces are much wider than those in the printed facsimile and the result is not pleasing in either version. Presumably this is due to a "one pass" line breaking algorithm (rather than TeX's search for a "least bad" set of line breaks) and, in consequence, fewer hyphenations.
 Signature Ben.
Ben C - 21 May 2008 21:28 GMT [...]
>> There is no way to achieve it directly in CSS, even when using the >> proposed and partly implemented text-justify property. However, you [quoted text clipped - 11 lines] > line breaking algorithm (rather than TeX's search for a "least bad" > set of line breaks) and, in consequence, fewer hyphenations. Does your browser do _any_ hyphenations? Mine doesn't.
Interestingly the text contains soft hyphen (U+00AD) characters (in accomp-lishment) for example.
These have been discussed here before. From what I remember they started life as a hyphen but that programs like text editors were invited to move or remove if they joined lines (in the same way they move and remove newlines when they reformat paragraphs). But they have evolved instead into something that's supposed to mark hyphenation opportunities, which looks like how they're being used here.
Ben Bacarisse - 21 May 2008 23:55 GMT > [...] >>> There is no way to achieve it directly in CSS, even when using the [quoted text clipped - 14 lines] > > Does your browser do _any_ hyphenations? Mine doesn't. It[1] breaks accomp/lishment at the soft hyphen.
> Interestingly the text contains soft hyphen (U+00AD) characters (in > accomp-lishment) for example. [quoted text clipped - 5 lines] > instead into something that's supposed to mark hyphenation > opportunities, which looks like how they're being used here. I missed them at first since my view-source ends up calling an editor (gedit) which does as you describe -- it chooses not to show them unless the line wraps at that point. At first I thought the browser was being very clever (doing its own language dependent hyphenation) but I see now it was give some help.
[1] Epiphany 2.22.1.1, using gecko-1.9. Unsurprisingly firefox 3b shows the same behaviour at some font sizes.
 Signature Ben.
Jukka K. Korpela - 21 May 2008 23:57 GMT Scripsit Ben Bacarisse:
> For me, the most revealing thing is how > bad my browser is at justification. All browsers are bad at it. To be honest, IE is, for a change, probably less bad than others in this issue.
Browsers generally do just simple, even trivial justification, which adds spacing between words, distributing it evenly. IE lets the author make some suggestions on this, though. Notes on such topics: http://www.cs.tut.fi/~jkorpela/www/justify.html
> Almost all the spaces are much > wider than those in the printed facsimile and the result is not > pleasing in either version. Presumably this is due to a "one pass" > line breaking algorithm (rather than TeX's search for a "least bad" > set of line breaks) and, in consequence, fewer hyphenations. Browsers indeed do "one pass" line breaking and, worse still, do it simply but with some oddities. They don't hyphenate except at explicit hyphens or soft hyphens, and many browsers don't do even that, though the situation has improved.
My demo page was somewhat tuned, through the addition of soft hyphens, which produce reasonable line breaking opportunities especially when the primarily suggested font (Cambria) is used. Such fine-tuning is usually not very useful except for dealing with very long words that would otherwise create very ragged right hand side for text.
 Signature Jukka K. Korpela ("Yucca") http://www.cs.tut.fi/~jkorpela/
Andreas Prilop - 22 May 2008 14:45 GMT > Subject: Re: TeXâ?Ts Is this Klingon?
Jon Fairbairn - 23 May 2008 09:31 GMT >> Subject: Re: TeXâ?Ts > > Is this Klingon? Yes. It's the name of an opera with scenes in mime.
 Signature Jón Fairbairn Jon.Fairbairn@cl.cam.ac.uk
|
|
|