On Mon, Aug 02, 2004 at 03:14:44PM -0300, bulia byak wrote:
- tspans with sodipodi:role="line" are merged together, separated by spaces
[I've interpreted "separated by spaces" as "inserting a space character ( ) between each merged pair of spans".]
Inserting a space between joined words will do the wrong thing for URLs, hyphenated words, and probably Chinese text.
The problem shouldn't arise if we allow typing directly into a shape, with Inkscape doing the line breaking: Inkscape can retain the space characters where they exist, as well as retaining newlines.
[How would newlines be stored in SVG? Is newline recognized as such in the 1.2 draft spec, at least for textflows?]
Approaches until we support typing into a text shape:
- "Unix hacker's approach": Don't insert spaces. The user will compensate, either by not doing any line breaks, or by typing an explicit space (if appropriate) before line breaks. The spelling checker should pick up any mistakes made.
- "Microsoft approach": Use the xml:lang attribute to decide whether or not to insert spaces, and require the user to use a "none" language for URLs. Treat hyphenated words specially (if language is en etc.).
Issues:
- We don't yet support specifying xml:lang for text. (We should, e.g. for spell checking.)
- I don't know of a two-letter code suitable for "none". (xml:lang can be set to "none", but this is for overriding CSS rules, and is to be considered equivalent to absence of xml:lang.)
How should we treat absence of xml:lang? Currently the spell checker language is taken from locale (I forget which; I think LC_MESSAGES).
How should we treat unrecognized language codes?
pjrm.