Looking for an example of plain text which is obvious to anybody,
it seems to me that the Subject field of e-mails is a good example.
Common e-mail software lets you enter any text but gives you never
access to any higher-level protocol. Possibly you can select the font
in which the subject line
The Subject filed is subject to special encoding like
Quoted-Printable or Base64 using specific prefixes. This is necessary
because the MIME headers spreciying the ail encoding only applies to
the mail body but not to the headers themselves.
For this reason it is not stricly plain text.
On 7/20/2012 8:41 AM, Karl Pentzlin wrote:
Looking for an example of plain text which is obvious to anybody,
it seems to me that the Subject field of e-mails is a good example.
By common convention, certain notational features have been relegated to
styled text. Super and subscript in
2012-07-20 19:52, Philippe Verdy wrote:
The Subject fi[el]d is subject to special encoding like
Quoted-Printable or Base64 using specific prefixes.
This is a matter of character encoding. All plain text inevitably has
some encoding, and the encoding may vary without changing the plain text
A) it can use quoted-printable
B) See RFC 6532/6530 - Now it can be UTF-8 :)
-Shawn
I put together some notes on different ways for programming languages to
handle Unicode at a low level. Comments welcome.
http://macchiati.blogspot.com/2012/07/unicode-string-models-many-programming.html
Macchiato
»http://macchiati.blogspot.com/2012/07/unicode-string-models-many-programming.html
2012-07-20 20:19, Asmus Freytag wrote:
On 7/20/2012 8:41 AM, Karl Pentzlin wrote:
Looking for an example of plain text which is obvious to anybody,
it seems to me that the Subject field of e-mails is a good example.
By common convention, certain notational features have been relegated to
On Fri, Jul 20, 2012 at 1:31 PM, Mark Davis ☕ m...@macchiato.com wrote:
I put together some notes on different ways for programming languages to
handle Unicode at a low level. Comments welcome.
Macchiato »
Many programming languages (and most modern software) have moved to Unicode
model of
On 7/20/2012 1:34 PM, Jukka K. Korpela wrote:
2012-07-20 20:19, Asmus Freytag wrote:
On 7/20/2012 8:41 AM, Karl Pentzlin wrote:
Looking for an example of plain text which is obvious to anybody,
it seems to me that the Subject field of e-mails is a good example.
By common convention, certain
That means that it is best to optimize for BMP characters (and as a
subset, ASCII and Latin-1), and fall into a ‘slow path’ when a
supplementary character is encountered.
I'm concerned about the statement/implication that one can optimize
for ASCII and Latin-1. It's too easy for a lot of
Mark wrote: “I put together some notes on different ways for programming
languages to handle Unicode at a low level. Comments welcome.”
Nice article as far as it goes and additions are forthcoming. In addition to
multiple code units per character in UTF-8 and UTF-16, there are variation
Thanks, nice article. We got into some of those hair caret positioning
issues back at Apple; we even had a design that would associate a series of
lines (which could be slanted and positioned) with a ligature, but
ultimately 1/m gets you 99% of the value, with very little cost.
(My article was
On 2012/07/21 7:01, David Starner wrote:
I'm concerned about the statement/implication that one can optimize
for ASCII and Latin-1. It's too easy for a lot of developers to test
speed with the English/European documents they have around and test
correctness only with Chinese. I see the argument
13 matches
Mail list logo
