On 25-6-2012 16:50, Philipp Gesang wrote:
···date: 2012-06-25, Monday···from: Hans Hagen···
On 25-6-2012 15:39, Philipp Gesang wrote:
- Does the difference wrt node subtype matter assuming I only
(a) copy glyph nodes and (b) manipulate their .char field?
not that much, it's just a
···date: 2012-06-26, Tuesday···from: Hans Hagen···
On 25-6-2012 16:50, Philipp Gesang wrote:
···date: 2012-06-25, Monday···from: Hans Hagen···
On 25-6-2012 15:39, Philipp Gesang wrote:
- Does the difference wrt node subtype matter assuming I only
(a) copy glyph nodes and (b)
On 26-6-2012 14:08, Philipp Gesang wrote:
···date: 2012-06-26, Tuesday···from: Hans Hagen···
On 25-6-2012 16:50, Philipp Gesang wrote:
···date: 2012-06-25, Monday···from: Hans Hagen···
On 25-6-2012 15:39, Philipp Gesang wrote:
- Does the difference wrt node subtype matter assuming I
Hi all,
I need a (pre-linebreak) callback to behave the same way with the
Context and Plain formats. *The sequence that nodes are traversed
in is very important.* Afaict the callback will have to be
registered as a “processors”/“before” nodes task. However, the
behavior is not identical:
1. If
On 25-6-2012 15:39, Philipp Gesang wrote:
- Which node task gets me a behavior similar to the raw
pre_linebreak_filter?[*]
depends on what plain does ... anyway, 'before' is pretty raw i guess
- Does the difference wrt node subtype matter assuming I only
(a) copy glyph nodes
···date: 2012-06-25, Monday···from: Hans Hagen···
On 25-6-2012 15:39, Philipp Gesang wrote:
- Does the difference wrt node subtype matter assuming I only
(a) copy glyph nodes and (b) manipulate their .char field?
not that much, it's just a state signal for font processing
Good to
