TextRework - Revision history

Tavmjong: /* Strategy */

2012-07-04T03:04:13Z

Strategy

← Older revision		Revision as of 03:04, 4 July 2012
Line 14:		Line 14:
	== Strategy ==		== Strategy ==

	There are 3 types of text now: regular, flowed ~~and~~ linked-flowed text.		There are 4 types of text now: regular, flowed, linked-flowed text and text on a path. Text on a path is a special case that will be ignored for the moment.

	The major goal is to reorganize the code to treat all text as normal SVG text. Three special cases would be indicated by inkscape namespace tags giving a total of four types of text:		The major goal is to reorganize the code to treat all text as normal SVG text. Three special cases would be indicated by inkscape namespace tags giving a total of four types of text:

ZLv: what types of text is now

2012-06-27T09:13:30Z

what types of text is now

← Older revision		Revision as of 09:13, 27 June 2012
Line 13:		Line 13:

	== Strategy ==		== Strategy ==

			There are 3 types of text now: regular, flowed and linked-flowed text.

	The major goal is to reorganize the code to treat all text as normal SVG text. Three special cases would be indicated by inkscape namespace tags giving a total of four types of text:		The major goal is to reorganize the code to treat all text as normal SVG text. Three special cases would be indicated by inkscape namespace tags giving a total of four types of text:

Lajujula at 12:30, 25 May 2012

2012-05-25T12:30:56Z

← Older revision		Revision as of 12:30, 25 May 2012
Line 74:		Line 74:
	# Switch "normal" Inkscape text (with lines handled by Inkscape) to use the new code.		# Switch "normal" Inkscape text (with lines handled by Inkscape) to use the new code.
	# Rewrite line-breaking code to output standard SVG.		# Rewrite line-breaking code to output standard SVG.

			== Alignment Issues ==

			Note that inkscape is not able to vertically align some text according to a given boundary (wether the text box or an explicitly selected shape)
			It would be usefull to get such alignment features. Apple Pages does it "the right way"

Tavmjong: /* Inkscape flowed into shape text */

2012-03-29T18:31:04Z

Inkscape flowed into shape text

← Older revision		Revision as of 18:31, 29 March 2012
Line 66:		Line 66:
	Switching between the four modes would be possible, preserving the rendering of the text as		Switching between the four modes would be possible, preserving the rendering of the text as
	much as possible.		much as possible.

			Note: SVG2 will include text flow into arbitrary shapes using [http://dev.w3.org/csswg/css3-regions/ CSS Regions] and [http://dev.w3.org/csswg/css3-exclusions/ CSS Exlusions].

	== Implementation Steps ==		== Implementation Steps ==

Tavmjong: /* Inkscape flowed text */

2012-03-29T18:19:43Z

Inkscape flowed text

← Older revision		Revision as of 18:19, 29 March 2012
Line 48:		Line 48:
	could be used to justify the text.		could be used to justify the text.

	Hyphenation, indentation, etc. could be added here.		Hyphenation, indentation, etc. could be added here. Note that SVG2 may add some CSS text properties that could be useful here.

	New attributes:		New attributes:

Tavmjong: /* Normal SVG text */

2012-03-29T18:15:39Z

Normal SVG text

← Older revision		Revision as of 18:15, 29 March 2012
Line 25:		Line 25:
	One problem with the current Inkscape implementation is that text in a <text> object is		One problem with the current Inkscape implementation is that text in a <text> object is
	automatically moved to a <tspan>. This can cause problems with animated SVG's.		automatically moved to a <tspan>. This can cause problems with animated SVG's.

			A block of text should be contained in one <text> element. Multiple lines should be handled in <tspan>s. This allows multi-line text selection (for example, you may want to change an attribute on a string of text that spans parts of two lines).

	===Normal Inkscape text===		===Normal Inkscape text===

Tavmjong: /* Normal SVG text */

2012-03-29T18:13:07Z

Normal SVG text

← Older revision		Revision as of 18:13, 29 March 2012
Line 21:		Line 21:
	The only special text manipulating provided by Inkscape would be that a carriage return would create		The only special text manipulating provided by Inkscape would be that a carriage return would create
	a new <tspan> starting directly below the first "y" value of the <text> object and a distance of		a new <tspan> starting directly below the first "y" value of the <text> object and a distance of
	"line-spacing" below the <text> or <tspan> just before the carriage return.		"line-spacing" below the <text> or <tspan> just before the carriage return (this should work for both right-to-left text and left-to-right text).

	One problem with the current Inkscape implementation is that text in a <text> object is		One problem with the current Inkscape implementation is that text in a <text> object is

Tavmjong: Created page with '= Proposal for restructuring how Inkscape handles text.= This is a work in progress... == Motivation == Inkscape currently handles all text layout using code written for the n...'

2010-07-25T07:25:40Z

Created page with '= Proposal for restructuring how Inkscape handles text.= This is a work in progress... == Motivation == Inkscape currently handles all text layout using code written for the n...'

New page

= Proposal for restructuring how Inkscape handles text.=

This is a work in progress...

== Motivation ==

Inkscape currently handles all text layout using code written for the never-adopted "flowed-text" SVG1.2 spec. There are several problems with this code:

* The code does not handle normal SVG text well.
* It is extremely complex. It mixes up line-breaking with layout code.
* Inkscape's "flowed-text" is not recognized by any other SVG renderer.

== Strategy ==

The major goal is to reorganize the code to treat all text as normal SVG text. Three special cases would be indicated by inkscape namespace tags giving a total of four types of text:

===Normal SVG text===
Standard SVG text with all properties ("x", "y", "letter-spacing, etc.).

The only special text manipulating provided by Inkscape would be that a carriage return would create
a new <tspan> starting directly below the first "y" value of the <text> object and a distance of
"line-spacing" below the <text> or <tspan> just before the carriage return.

One problem with the current Inkscape implementation is that text in a <text> object is
automatically moved to a <tspan>. This can cause problems with animated SVG's.

===Normal Inkscape text===

Normal SVG text with the added property that lines are handled by Inkscape,
allowing insertion of new lines in the middle This is equivalent to the current Inkscape
manipulation of text.

New attributes:

* inkscape:text-property="manage_lines" : Indicates type
* inkscape:text-role="line" : Marks start of each new line (replaces sodipodi:role="line").

One routine would be responsible for manipulation of lines, outputting normal SVG which
would then be rendered by the normal SVG text routines.

===Inkscape flowed text===

Text where line-breaking would be handled by Inkscape to fit in a rectangle box,
equivalent to the current Inkscape flowed:text. "letter-spacing" and "word-spacing"
could be used to justify the text.

Hyphenation, indentation, etc. could be added here.

New attributes:

* inkscape:text-property="flowed_text"
* inkscape:text-align="justify"
* inkscape:text-box=href(#xxx) or <inkscape:flowregion>

One routine would be responsible for line-breaking, outputting normal SVG which would then
be rendered by the normal SVG text routines. Line spacing is controlled only by the "line-spacing"
property.. This routine would be responsible for verifying new lines fit in the box.

===Inkscape flowed into shape text===

A more generalized case of normal Inkscape flowed text.

Switching between the four modes would be possible, preserving the rendering of the text as
much as possible.

== Implementation Steps ==

# Write new routines to handle plain SVG text. Check that it works for all imported text.
# Switch "normal" Inkscape text (with lines handled by Inkscape) to use the new code.
# Rewrite line-breaking code to output standard SVG.