Your idea of propagation seems worth exploring - thanks!
On Mon, Oct 17, 2011 at 1:07 AM, Richard Wordingham
wrote:
> On Sun, 16 Oct 2011 21:37:20 +0200
> Peter Cyrus wrote:
>
>> Perhaps, awkwardly. But that is ultimately equivalent to marking the
>> gait on every letter, in which case I probab
It's been done already : the International Phonetic Alphabet. If we
all just wrote in that, it would make Unicode much easier to
implement, too.
I'm just working on Plan B, just in case.
On Mon, Oct 17, 2011 at 8:48 PM, Ken Whistler wrote:
> On 10/17/2011 1:23 AM, Peter Cyrus wrote:
>>
>> Perha
On 10/17/2011 1:23 AM, Peter Cyrus wrote:
Perhaps the idea of something embedded in the text that then controls
the display of the subsequent run of text is the very definition of
"markup", whether or not that markup is a special character or an
ASCII sequence like or.
Yep.
And FWIW, rather t
Perhaps the idea of something embedded in the text that then controls
the display of the subsequent run of text is the very definition of
"markup", whether or not that markup is a special character or an
ASCII sequence like or .
On Mon, Oct 17, 2011 at 1:07 AM, Richard Wordingham
wrote:
> On Sun
On Sun, 16 Oct 2011 21:37:20 +0200
Peter Cyrus wrote:
> Perhaps, awkwardly. But that is ultimately equivalent to marking the
> gait on every letter, in which case I probably wouldn't need to
> distinguish between initial and non-initial letters.
If you allow C(R)V(C) as a 'fixed' syllable struc
On Sat, 15 Oct 2011 04:37:11 +0200
Peter Cyrus wrote:
> Ken, your explanation seems more permissive than I had anticipated.
> One particularity of this script is that it is written in different
> "gaits", depending on the phonology of the language. Languages with
> open syllables, like most Nig
Ken, your explanation seems more permissive than I had anticipated.
Your example of "32" would seem to me at risk of behaving
in unforeseen ways if, for instance, it were split up. Wouldn't it
match a string "up > 2"? Wouldn't it fail to match 3²? I guess I
thought that plain text should be mor
On 10/14/2011 11:47 AM, Joó Ádám wrote:
Peter asked for what the Unicode Consortium considers plain text, ie.
what principles it apllies when deciding whether to encode a certain
element or aspect of writing as a character. In turn, you thoroughly
explained that plain text is what the Unicode Con
Ken,
Peter asked for what the Unicode Consortium considers plain text, ie.
what principles it apllies when deciding whether to encode a certain
element or aspect of writing as a character. In turn, you thoroughly
explained that plain text is what the Unicode Consortium considered to
be plain text
On 10/13/2011 10:49 PM, Peter Cyrus wrote:
Is there a definition or guideline for the distinction between plain
text and rich text?
I think where you may be getting hung up is trying to define plain
text versus rich text in terms of the content and/or appearance of
the text (i.e. the outcome)
On Fri, Oct 14, 2011 at 9:49 AM, Peter Cyrus wrote:
> For that matter, perhaps the normal space is a type of markup, especially when
> it triggers the use of a final variant in the previous character.
Not the following space, but a word boundary triggers the use of a
final variant in the previous
Is there a definition or guideline for the distinction between plain
text and rich text?
For example, in the expression 3², the exponent is a single character,
"superscript two". Semantically, this expression is equivalent to
3^2, using a visible character to indicate exponentiation and then
leav
12 matches
Mail list logo
