Named strings

bertfrees commented 9 years ago

[x] Support an optional second argument for ‘string()’ for defining the "search function". Add values based on actual use cases. Below is an overview of possible search functions and a comparison between CSS, OBFL and FO. Existing values are marked in bold.

CSS	obfl:marker-reference direction/scope	fo:retrieve-marker retrieve-position/retrieve-boundary
first	forward/page backward/before-page	first-including-carryover/document?
start	backward/before-page-content
	backward/before-page
last	backward/document
first-except	"" if forward/page else backward/before-page
	backward/sequence
	forward/sequence
	forward/page	first-including-carryover/page?
	backward/page
first-on-page	forward/page-content
last-on-page	backward/page
spread-start	backward/before-page-spread-content
last-on-spread	backward/page-spread
	forward/volume
	backward/volume

[ ] spread-foo should behave like foo if it is the first page of a volume (i.e. if there is no left page). (See also https://github.com/joeha480/dotify/issues/144.)
[x] Keyword last-except-start
[x] Named strings are for unformatted text.
[x] Explain that implementations are responsible for ensuring that the result after evaluation of the string() function is a braille string. The text transformation happens after string() and not before string-set! This means that the transformation can be influenced by the effective value of 'text-transform' at the place of insertion, but not by the value of 'text-transform' at the original position in the DOM.
[x] content() should only contain the text and not the text of '::after' and '::before' pseudo-elements (see http://www.w3.org/TR/css3-gcpm/#content-function-header).
[x] Describe that 'string-set' on elements with 'display: none' (and their descendants) still has the same effect. Use case: set string values from metadata in header or pagenum elements.
[ ] Should string() be allowed in the content properties of (pseudo-)elements? How should the search function behave in this case?
[ ] Is string-set evaluated at an element's original position in the DOM?
[ ] Is string() evaluated at an element's original position in the DOM?
[ ] Explain that the identifiers ‘print-page’, ‘running-header’ and ‘running-footer’ have a special meaning in the Liblouis based implementation.
[ ] A more powerful alternative for running headers and footers is to use the ‘running()’ value of position and the ‘element()’ value of content [CSS3GCPM]. A proposed alternative syntex with a ‘running’ property and a ‘:running’ pseudo-class also allows copying (rather than just moving) elements. [PRINCE] defines yet another alternative with a ‘flow’ property and a ‘flow()’ value for ‘content’.
[ ] List differences with plain CSS.
[ ] Keywords start-except-last and spread-start-except-last: https://github.com/braillespecs/braille-css/issues/43
[ ] The definition of page-start currently says nothing about the case when there are content boxes preceding the first assignment on the page and there is no entry value, so in that case the result is the empty string, and not, as some might expect, the first value on the page (page-first). Consider changing the definition as to make it more useful.

braillespecs / braille-css

Named strings #17

Named strings