tim: are you speaking of heavy metal fonts? Then yes, technology is
rock-solid.
These guys had all sort of space width available...
The rules for using the right space can be complex, but we have our own too
(padding/kerning).
But concerning CharacterBlockScanner, I'm more on electronic artifacts:
the explicitation of invisible spacing characters when selecting some
text...
For rightFlush, the typographers knowledge can also help, but when I think
of it, the rules seem obvious to me now:
align right of last char on each line.


2013/9/29 tim Rowledge <tim at rowledge.org>

> That is opening a can of very scary worms, with large amounts of super-hot
> pepper added, and liquorice (I hate it).
>
> My starting point is "let's keep it as simple as possible even if it might
> be wrong, unless it really annoys us". We can always make it more
> correct(er)  later(er).
>
> I think the approach generally would be along the lines of 'spaces only
> count between non-space characters'. Uh, then it gets complicated when a
> space (or more than one) is at the start of the line. Or at the end. Or in
> the middle, when there is a tab as well.
>
> OK, so it isn't simple. Bugger.
>
> What *should* damn well be simple is finding some authoritative source to
> tell us what should happen. This isn't rocket science - it's stuff that has
> been sorted for centuries by skilled typographers. Somebody, somewhere, has
> written down the proper thing to do. All we need to do is find it...
>
>
> tim
> --
> tim Rowledge; tim at rowledge.org; http://www.rowledge.org/tim
> Strange OpCodes: DUL: Delete Utility Library
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20130930/85426b12/attachment.htm