Kenneth re-iterated:
>Dean continued:
>
>> Or (making the missed point explicit):
>
>I attempted to bring this thread back on track yesterday, but
>since it seems to have veered off into the ditch again, we
>may as well spin our wheels some more, I guess. :-(
My response to your assessment was th
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
> Behalf Of Dean Snyder
> I have brought
> up a multitude of different arguments over the past few weeks against
> this proposal.
I certainly don't recall a multitude of different arguments from you,
though perhaps I've gotten tired of heari
Michael Everson wrote at 11:25 PM on Friday, May 21, 2004:
>At 16:01 -0400 2004-05-21, Dean Snyder wrote:
>>I was responding to Michael's positive assertion that he has "yet to find
>>a single font with Hebrew encoding and Phoenician glyphs". The weight of
>>that statement is directly proportional
Dean Snyder wrote,
> But hammering on the same nail with the same hammer can drive it home.
Excellent response!
> Nevertheless, even though I may be stupid, ...
I don't think you're stupid.
There may come a time in which we find ourselves arguing on the
same side of a proposition. I look
From: "E. Keown"
> Elaine Keown
> Tucson
>
> Dear Bob Richmond:
>
> At last, a helpful suggestion!!!
>
> > 4. Many users of ancient scripts are not specialists
> > in all (or any) of the scripts they want to work
> > with. Software needs to recognise this and provide
>
> This i
Dean Snyder wrote:
What do you suggest I, or others, do other than have such discussions?
Target precisely and selectively.
Pay attention to what Ken Whistler writes, as he can generally be relied on to precisely
identify the basis on which a UTC decision might be expected. As he has noted, UTC
a
Dean Snyder wrote,
> Or (making the missed point explicit):
>
> 6) Show that the basic assumption behind the question, "lots of potential
> users demonstrates the usefulness of an encoding", is in fact a bad
> assumption, and one the UTC itself does not consider decisive.
It's possible that I'
At 03:34 PM 5/21/2004, Dean Snyder wrote:
Doug Ewell wrote at 3:07 PM on Friday, May 21, 2004:
>Dean Snyder wrote:
>
>> ... And since Japanese and Fraktur are not separately encoded just
>> because there would be lots of people who would use such an encoding,
>> why would you, on that same faulty
From: "Michael Everson" <[EMAIL PROTECTED]>
> At 22:04 +0200 2004-05-21, Philippe Verdy wrote:
>
> >I have no référence in my French dictionnaries for "Gotique", but LOTS of
> >references to "écriture gothique" ou "caractères gothiques" (including on the
> >web and in calligraphy/typography books).
At 19:00 -0400 2004-05-21, Dean Snyder wrote:
>>>Furthermore, this has the advantage of side-stepping the whole
issue of the origins of the Greek alphabet along with its
subsequent Mediterranean script descendants, while not mucking up
Canaanite which is already encoded in Unicode, albeit somewhat
Dean continued:
> Or (making the missed point explicit):
I attempted to bring this thread back on track yesterday, but
since it seems to have veered off into the ditch again, we
may as well spin our wheels some more, I guess. :-(
> If the UTC did consider the potential for large numbers of users
Michael Everson wrote:
Collins-Robert Senior Dictionnaire FranÃais-Anglais Anglais-FranÃais
gothique [architecture, style] Gothic. Ãcriture ~ Gothic script
That means Fraktur
gotique [ling] Gothic
That means Wulfilan
Stet.
Le Petit Robert (1987) concurs with your assement:
---
GOTIQUE. Voir GOTH
Anyone have any comments about the numbers proposed for the
Phoenician encoding?
--
Michael Everson * * Everson Typography * * http://www.evertype.com
Michael Everson wrote at 10:45 PM on Friday, May 21, 2004:
>At 14:35 -0400 2004-05-21, Mark E. Shoulson wrote:
>>Dean Snyder wrote:
>>
>>>Furthermore, this has the advantage of side-stepping the whole
>>>issue of the origins of the Greek alphabet along with its
>>>subsequent Mediterranean script
John Hudson wrote at 3:17 PM on Friday, May 21, 2004:
>Dean Snyder wrote:
>
>>>those who oppose the encoding would better spend
>>>their time querying that need directly to the people who have expressed
>>>it than making
>>>silly, repetetive arguments about fraktur on this list.
>
>> Silly, it i
At 18:34 -0400 2004-05-21, Dean Snyder wrote:
I've never said there was a demand for it; I've only said that lot's of
people would USE it if it were encoded. That is my opinion. Do you
disagree that lots of people would use a Fraktur encoding?
We already have one. No, people are not flocking to enc
Philippe Verdy a écrit :
To find proof that "gotique" is incorrect in French, I looked for some official
French resources, notably the list of language names published and used by the
BPI:
http://www.culture.gouv.fr/culture/dglf/bpi/list-langues.html
clicking in the "allemand" language name gives t
At 16:01 -0400 2004-05-21, Dean Snyder wrote:
>The burden of proof for this
>is on those making the suggestion. Michael has simply said he has never
seen such a font. If you want to support the claim, you cannot simply
question how thoroughly Michael has searched -- it's not his
responsibility. I
Doug Ewell wrote at 3:07 PM on Friday, May 21, 2004:
>Dean Snyder wrote:
>
>> ... And since Japanese and Fraktur are not separately encoded just
>> because there would be lots of people who would use such an encoding,
>> why would you, on that same faulty basis, support a separate encoding
>> for
Dean Snyder wrote:
those who oppose the encoding would better spend
their time querying that need directly to the people who have expressed
it than making
silly, repetetive arguments about fraktur on this list.
Silly, it is not; repetitive, only because the argument is apropos, has
never been co
At 12:01 -0700 2004-05-21, John Hudson wrote:
What in the encoding of 'Phoenician' characters in Unicode obliges
anyone to use those characters for ancient Canaanite texts?
Nothing. People often already represent these texts in Hebrew or
Latin transliteration.
--
Michael Everson * * Everson Typog
Patrick Durusau wrote at 4:34 PM on Friday, May 21, 2004:
>Dean,
>
>Dean Snyder wrote:
>> Mark E. Shoulson wrote at 2:35 PM on Friday, May 21, 2004:
>>>Can we live cosmetic issues like the name out of it? OK, so "Hebrew" is
>>>really "Jewish Aramaic," and it's ironic that we're working on encodi
Dean Snyder wrote:
> ... And since Japanese and Fraktur are not separately encoded just
> because there would be lots of people who would use such an encoding,
> why would you, on that same faulty basis, support a separate encoding
> for Phoenician?
Where are you getting this from?
You asserted
Collins-Robert Senior Dictionnaire Français-Anglais Anglais-Français
gothique [architecture, style] Gothic. écriture ~ Gothic script
That means Fraktur
gotique [ling] Gothic
That means Wulfilan
Stet.
--
Michael Everson * * Everson Typography * * http://www.evertype.com
Philippe Verdy wrote:
>> In any case, the question of *which* French-based transliteration(s)
>> to use seems to have been decided already.
>
> Is it true also for NÂ=206, Code=Goth, English_Name="Gothic",
> Nom_franÃais="Gotique", Property_Value_Alias="Gothic" ?
I have no idea. I was only refe
Philippe Verdy scripsit:
> There are many confusions in French with the meaning of the term "gothique",
"Gothic" and "gothic" have exactly the same confusions in English, with the
addition of a subculture of people who dress in a rather unusual fashion.
--
Dream projects long deferred
At 14:35 -0400 2004-05-21, Mark E. Shoulson wrote:
Dean Snyder wrote:
Furthermore, this has the advantage of side-stepping the whole
issue of the origins of the Greek alphabet along with its
subsequent Mediterranean script descendants, while not mucking up
Canaanite which is already encoded in U
Doug Ewell wrote:
Dean Snyder wrote:
You're missing my point. I don't really care that it's called Hebrew;
but I suspect that OTHERS do and that is one motivation (maybe even a
subconscious one) behind a separate Phoenician proposal.
I doubt anyone's this badly snowed by the naming convent
Philippe Verdy scripsit:
> But today the global httd.conf does not specify any charset in the content-type,
In fact I have seen the current httpd.conf, and it does specify UTF-8 as the
DefaultCharset.
--
"While staying with the Asonu, I met a man from John Cowan
the Candensian plane, which
At 22:04 +0200 2004-05-21, Philippe Verdy wrote:
I have no référence in my French dictionnaries for "Gotique", but LOTS of
references to "écriture gothique" ou "caractères gothiques" (including on the
web and in calligraphy/typography books). I think it's a typo here... So this
should be Nom_frança
At 21:38 +0200 2004-05-21, Philippe Verdy wrote:
Michael said that he will ignore all differences found in the previous HTML
files, considering only the text file as the source and adding the missing
elements.
Yes, I did.
Since then, there has been no clear justification for the removal of Georgian
To find proof that "gotique" is incorrect in French, I looked for some official
French resources, notably the list of language names published and used by the
BPI:
http://www.culture.gouv.fr/culture/dglf/bpi/list-langues.html
clicking in the "allemand" language name gives this:
http://www.culture.g
James Kass wrote at 7:22 AM on Friday, May 21, 2004:
>Doug Ewell responded to Dean Snyder,
>
>> James Kass pointed out that fears of large numbers of people adopting a
>> Phoenician Unicode encoding would demonstrate the usefulness of the
>> encoding. You responded that the same was true for Fra
John Hudson wrote at 12:01 PM on Friday, May 21, 2004:
>those who oppose the encoding would better spend
>their time querying that need directly to the people who have expressed
>it than making
>silly, repetetive arguments about fraktur on this list.
Silly, it is not; repetitive, only because t
Philippe Verdy a écrit :
Please check http://www.inalco.fr/
As the splash page shows it is « Langues O' ».
Yes but only on the splash screen. Elsewhere on the site (the top banner, and
menu, and the logos in PDFs of its brochures, letters and publications) it uses
"Langues'O" which means "Lang
Michael Everson wrote:
At 08:31 -0700 2004-05-21, Mark Davis wrote:
I am not very happy about loading the plain-text in browsers. Three
of my browsers load it and *all* the French UTF-8 is displayed in
Latin 1.
Michael, you just need to put a BOM at the start of the file. Direct
access to
the p
From: "Patrick Andries" <[EMAIL PROTECTED]>
> From: "John Cowan" <[EMAIL PROTECTED]>
> >> Philippe Verdy scripsit:
> >> >C'est quoi Langues'O ? Où est-ce ?
>
> Please check http://www.inalco.fr/
>
> As the splash page shows it is « Langues O' ».
Yes but only on the splash screen. Elsewhere on the
Dean,
Dean Snyder wrote:
Mark E. Shoulson wrote at 2:35 PM on Friday, May 21, 2004:
Can we live cosmetic issues like the name out of it? OK, so "Hebrew" is
really "Jewish Aramaic," and it's ironic that we're working on encoding
a Samaritan block distinct from the Hebrew block. Lots of things
Dean Snyder wrote:
> You're missing my point. I don't really care that it's called Hebrew;
> but I suspect that OTHERS do and that is one motivation (maybe even a
> subconscious one) behind a separate Phoenician proposal.
I doubt anyone's this badly snowed by the naming conventions. I suspect
t
Michael Everson wrote at 2:53 PM on Friday, May 21, 2004:
>At 05:30 + 2004-05-21, James Kass wrote:
>
>>As a member of the Latin script user community, I'd not be threatened by
>>a separate encoding for Fraktur.
Would you recommend, for example, Google for ubiquitous searching for
textually-
From: "Doug Ewell" <[EMAIL PROTECTED]>
> In any case, the question of *which* French-based transliteration(s) to
> use seems to have been decided already.
Is it true also for NÂ=206, Code=Goth, English_Name="Gothic",
Nom_franÃais="Gotique", Property_Value_Alias="Gothic" ?
My French dictionnaries
Peter Kirk suggested:
> Similarly, I suppose, with the proposed Phoenician script: each
> character could be given a compatibility decomposition to the equivalent
> Hebrew letter. This implies automatic interleaved collation. Now, while
> I don't expect Michael Everson to jump at this suggestio
Peter Constable wrote at 7:53 AM on Friday, May 21, 2004:
>Dean, the suggestion has been that people want to or are encoding PH
>text using the Hebrew block of Unicode and simply displaying with a font
>that uses PH glyphs for those characters.
I missed that assertion - who made it?
>The burde
Mark E. Shoulson wrote at 2:35 PM on Friday, May 21, 2004:
>Dean Snyder wrote:
>
>>Furthermore, this has the advantage of side-
>>stepping the whole issue of the origins of the Greek alphabet along with
>>its subsequent Mediterranean script descendants, while not mucking up
>>Canaanite which is al
From: "Peter Constable" <[EMAIL PROTECTED]>
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> On Behalf
> > Of Philippe Verdy
>
> > I updated my own Excel sheet at:
>
> Philippe, I really appreciate the content you posted for it's potential
> value in guiding the RA in doing a better job with
Doug asked:
> I'm sure this is a dumb question, but why would there be any pages in
> non-Unicode charsets on the Unicode Web site?
Legacy, just as for many sites.
The question is whether it makes sense to go back to
older, archived material and:
a. delete it, because it is in Latin-1 or CP 1
Philippe Verdy scripsit:
> You can instruct Apache to serve a part of the site with another default
> encoding by uploading with your FTP client a .htaccess file containing a
> different default MIME type association.
.htaccess cannot do anything that hacking the httpd.conf file can't do.
In this
From: <[EMAIL PROTECTED]>
> Jon Hanna scripsit:
>
> > [T]he default encoding on the server (which really should be utf-8
> > on www.unicode.org at this stage).
>
> Currently it is, but there are sticky issues: in particular, a default
encoding
> overrides information in HTML meta elements as well a
From: "Mark Davis" <[EMAIL PROTECTED]>
> Use of is perfectly appropriate to allow line breaks. What is not yet
> being done is to *disallow* line breaks in the dates; that is a mistake, since
> IE will break in dates and numbers, e.g.
NO. You did not understand the issue. It is incorrectly enco
Ted Hopp wrote:
I don't think this expectation is unreasonable,
given their perception of the standard, and perhaps Unicode needs to do a
better job in conveying what the standard is and does and how it can be used.
With all due respect, this is disingenuous.
It was intended to be helpful.
It's li
Doug Ewell scripsit:
> John Cowan wrote:
>
> > Consequently, random pages that happen to be in non-Unicode charsets
> > are getting mis-served and mis-displayed. The site will probably
> > revert to having no default as a result, which is a great pity.
>
> I'm sure this is a dumb question, but
"Patrick Andries" wrote
>
> If many Israelis may not be able to read Phoenician or Neo-Punic, it is
> not obvious to me that Phoenician or Punic scholars -- presumably the
> intended users of Phoenician/Canaanite -- do not read Square Hebrew. I
> have some testimony to the opposite : Lionel Galand
John Cowan wrote:
> Consequently, random pages that happen to be in non-Unicode charsets
> are getting mis-served and mis-displayed. The site will probably
> revert to having no default as a result, which is a great pity.
I'm sure this is a dumb question, but why would there be any pages in
non
Dean Snyder wrote:
Furthermore, this has the advantage of side-
stepping the whole issue of the origins of the Greek alphabet along with
its subsequent Mediterranean script descendants, while not mucking up
Canaanite which is already encoded in Unicode, albeit somewhat
"prematurely", or "misnamed",
Elaine Keown
Tucson
Dear Bob Richmond:
At last, a helpful suggestion!!!
> 4. Many users of ancient scripts are not specialists
> in all (or any) of the scripts they want to work
> with. Software needs to recognise this and provide
This is true---absolutely. But since all of
ARABIC PERCENT SIGN (U+066A) has Line Break class ALPERCENT SIGN (U+0025) has Line Break class PO, as doPER MILLE SIGN (U+2030) and PER TEN THOUSAND SIGN(U+2031). All other properties appear to be identical for allfour characters Including being in Bidi Class ET. Given itsusage in URL's if you ha
Mark Davis wrote:
> Use of is perfectly appropriate to allow line breaks.
They show up as boxes on my system. Change fonts? Sure, I'd love to,
but the stylesheet wants to display the page in Arial:
BODY {
margin: 0; COLOR: #00; FONT-FAMILY: Arial, Geneva, sans-serif;
BACKGROUND-COLOR:
Jon Hanna scripsit:
> This is passing strange, for the problem was UTF-8 being mis-interpreted as a
> legacy encoding, not the other way around.
a) Not everyone uses a modern browser.
2) The problem might have been speculative (or memorious) rather than actual.
--
John Cowan
Quoting "[EMAIL PROTECTED]" <[EMAIL PROTECTED]>:
> Jon Hanna scripsit:
>
> > [T]he default encoding on the server (which really should be utf-8
> > on www.unicode.org at this stage).
>
> Currently it is, but there are sticky issues: in particular, a default
> encoding
> overrides information in
Antoine Leca wrote:
>> So there's nothing wrong if "Han'gul" is shown to users
>
> Sorry: this is meaningless to me as French reader. And it is a mistake
> (missing breve) when it comes about the McCune-Reischauer scheme.
> Half-good fallback mechanisms are usually better than nothing, but
> wors
Jon Hanna scripsit:
> [T]he default encoding on the server (which really should be utf-8
> on www.unicode.org at this stage).
Currently it is, but there are sticky issues: in particular, a default encoding
overrides information in HTML meta elements as well as browser heuristics,
at least for mod
> Use of is perfectly appropriate to allow line breaks.
> What is not yet being done is to *disallow* line breaks in the dates;
> that is a mistake, since IE will break in dates and numbers, e.g.
> the number -
> 3.
Yes, but... In this particular set of files, no matter *HOW* narrow I made
the
On Friday, May 21, 2004 12:06 AM, James Kass wrote:
> Doesn't the idea that so many people will embrace a new Phoenician range
> imply that it's the right thing to do?
No. It implies that Unicode calls the shots, for better or worse. I don't
accept that might makes right.
Ted
Ted Hopp, Ph.D.
Zi
Quoting Michael Everson <[EMAIL PROTECTED]>:
> At 15:39 +0100 2004-05-21, Jon Hanna wrote:
>
> >Were the headers correct?
>
> It is plain text.
HTTP has headers separate to the content (the headers come first and the content
comes next). These headers can contain encoding information and other
On Thursday, May 20, 2004 10:45 PM, John Hudson wrote:
Subject: Re: Response to Everson Phoenician and why June 7?
> It
> must seem pretty obvious to engineers that this is a standard for encoding
characters and
> that implementing support for the standard does not, per se, imply much of
anything a
At 07:57 -0700 2004-05-21, Curtis Clark wrote:
on 2004-05-21 07:10 Michael Everson wrote:
I am not very happy about loading the plain-text in browsers. Three
of my browsers load it and *all* the French UTF-8 is displayed in
Latin 1.
This *may* be a server issue. Iirc, the server has to be told to
At 08:03 -0700 2004-05-21, Peter Constable wrote:
Could everyone please exercise good editorial practice on their
postings? It's ridiculous to have to scroll to the third screen-full of
text to find where the poster's comments begin.
I'd really like people to paste the Unicode into the To field. I
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
> Of Michael Everson
> >As a side note to Michael or the other 6 RA members (Ken, and Rick
notably), I
> >don't think it's even a good idea to ZIP this reference plain-text
file due to
> >its very small size (which smaller than each of
At 08:31 -0700 2004-05-21, Mark Davis wrote:
> I am not very happy about loading the plain-text in browsers. Three
of my browsers load it and *all* the French UTF-8 is displayed in
Latin 1.
Michael, you just need to put a BOM at the start of the file. Direct access to
the plain text file, would
At 12:31 +0200 2004-05-21, Philippe Verdy wrote:
- "light blue" signals the english or French names that have been kept when
removing duplicate rows with alternate names.
Those duplicate rows did not appear in the plain-text data files, so
will not be considered further or tracked on the code chan
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
> Of Philippe Verdy
> I updated my own Excel sheet at:
Philippe, I really appreciate the content you posted for it's potential
value in guiding the RA in doing a better job with their data.
I hope, however, that you do not plan to lea
At 08:14 -0700 2004-05-21, Peter Constable wrote:
Doug's point is, if there are *lot* of people that will use a separate
Phoenician block, then that will validate that it was a useful thing to
do; but if there are *not*, then the unification-camp has little cause
for concern about existence of dist
> I am not very happy about loading the plain-text in browsers. Three
> of my browsers load it and *all* the French UTF-8 is displayed in
> Latin 1.
Michael, you just need to put a BOM at the start of the file. Direct access to
the plain text file, would be much preferred. The file is small -- the
Michael Everson wrote:
>> The plain text would appear directly in the browser window where it
>> could be saved as well, without needing any ZIP tool...
>
> Everyone has a zip tool.
>
> I am not very happy about loading the plain-text in browsers. Three
> of my browsers load it and *all* the Fren
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
> Of Dean Snyder
> >Who has ever asked for that?
>
> I have no one in mind.
>
> But, by analogy, so should no one think thusly about Phoenician (which
is
> to Jewish Hebrew script what Fraktur is to Roman German script).
I think Doug
At 15:39 +0100 2004-05-21, Jon Hanna wrote:
Were the headers correct?
It is plain text.
--
Michael Everson * * Everson Typography * * http://www.evertype.com
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf
> Of Dean Snyder
> >That proves nothing at all. In fact, I have a number of Phoenician
> >fonts using Latin clones to represent Phoenician letters. I have yet
> >to find a single font with Hebrew encoding and Phoenician glyphs.
>
> Whe
on 2004-05-21 07:10 Michael Everson wrote:
I am not very happy about loading the plain-text in browsers. Three of
my browsers load it and *all* the French UTF-8 is displayed in Latin 1.
This *may* be a server issue. Iirc, the server has to be told to mark
the text/plain MIME-type as UTF-8, since
Could everyone please exercise good editorial practice on their
postings? It's ridiculous to have to scroll to the third screen-full of
text to find where the poster's comments begin.
Peter
Peter Constable
Globalization Infrastructure and Font Technologies
Microsoft Windows Division
> >As a side note to Michael or the other 6 RA members (Ken, and Rick notably),
> I
> >don't think it's even a good idea to ZIP this reference plain-text file due
> to
> >its very small size (which smaller than each of the HTML versions of
> >codelists).
>
[snip]
> Everyone has a zip tool.
>
>
From: "John Cowan" <[EMAIL PROTECTED]>
Philippe Verdy scripsit:
Please go to Langues'O for this commentary. As I wrote, you will be
probably answered with the historical context.
C'est quoi Langues'O ? Où est-ce ?
Please check http://www.inalco.fr/
As the splash page shows it is « Lan
Use of is perfectly appropriate to allow line breaks. What is not yet
being done is to *disallow* line breaks in the dates; that is a mistake, since
IE will break in dates and numbers, e.g.
the number -
3.
Mark
__
http://www.macchiato.com
â à
saqqara a écrit :
Unification of the Phoenician script with Hebrew would certainly
eliminate some short term problems - the Hebrew script is fairly well
supported nowadays among applications and we'd eliminate the Plane 1
issue. Terribly confusing to users however - the majority do not read
H
At 10:28 +0200 2004-05-21, Philippe Verdy wrote:
From: "Michael Everson" <[EMAIL PROTECTED]>
At 23:21 +0200 2004-05-20, Philippe Verdy wrote:
>There is still a conflict of "Code" for Mandaean, is it "Mand" or "Mnda"?
Mand.
OK This is now corrected on the new HTML pages.
But the new "normative" p
At 05:30 + 2004-05-21, James Kass wrote:
As a member of the Latin script user community, I'd not be threatened by
a separate encoding for Fraktur. I have Fraktur books in my library.
Whether I've got their titles stored in my database using Latin characters
or abusing math variables is best le
At 00:10 -0400 2004-05-21, Dean Snyder wrote:
James Kass wrote at 4:06 AM on Friday, May 21, 2004:
Doesn't the idea that so many people will embrace a new Phoenician range
imply that it's the right thing to do?
Doesn't the idea that so many people will embrace a new Fraktur range
imply that it's th
From: "John Cowan" <[EMAIL PROTECTED]>
> Philippe Verdy scripsit:
>
> > > Please go to Langues'O for this commentary. As I wrote, you will be
> > > probably answered with the historical context.
> >
> > C'est quoi Langues'O ? Où est-ce ?
>
> Please forgive me for intruding into an internal francoph
A few (of many possible) points from a software
developers perspective on Phoenician proposal.
1. Assignment of Unicode characters is only a small
part of working with ancient scripts. For instance markup schemes such as XML to
distinguish languages, ideoms, dialects etc. is essential to de
Philippe Verdy scripsit:
> > Please go to Langues'O for this commentary. As I wrote, you will be
> > probably answered with the historical context.
>
> C'est quoi Langues'O ? Où est-ce ?
Please forgive me for intruding into an internal francophone matter, but
whenever I see "Langues'O", my mind
From: "Anto'nio Martins-Tuva'lkin" <[EMAIL PROTECTED]>
> Why the general Category of U+0482 : CYRILLIC THOUSANDS SIGN is So
> [Symbol, Other] while the apparently equivalent characters in the
> U+2160 - U+2183 range are rather Nl [Number, Letter].
>
> Granted that U+0482 is not a letter, but IMHO i
From: "Antoine Leca" <[EMAIL PROTECTED]>
> On Thursday, May 20th, 2004 23:56, Philippe Verdy wrote:
>
> > I see no real problem if not all the different orthographies are
> > listed or if they are not used universally. As long as the name is
> > non ambiguous. What will be important for interchange
Philippe Verdy wrote:
> Michael Everson wrote:
> > Philippe Verdy wrote:
> > >There is still a conflict of "Code" for Mandaean, is it "Mand" or "Mnda"?
> >
> > Mand.
>
> OK This is now corrected on the new HTML pages.
> But the new "normative" plain-text file now contains... "Mnda" !!!
I updated m
On Thursday, May 20th, 2004 23:56, Philippe Verdy wrote:
> I see no real problem if not all the different orthographies are
> listed or if they are not used universally. As long as the name is
> non ambiguous. What will be important for interchange of data will
> not be this name but the Code (or
From: "Michael Everson" <[EMAIL PROTECTED]>
> At 23:21 +0200 2004-05-20, Philippe Verdy wrote:
> >There is still a conflict of "Code" for Mandaean, is it "Mand" or "Mnda"?
>
> Mand.
OK This is now corrected on the new HTML pages.
But the new "normative" plain-text file now contains... "Mnda" !!!
21. mai. 2004 kello 07.30, James Kass kirjoitti:
As a member of the Latin script user community, I'd not be threatened
by
a separate encoding for Fraktur. I have Fraktur books in my library.
Whether I've got their titles stored in my database using Latin
characters
or abusing math variables is
Doug Ewell responded to Dean Snyder,
> James Kass pointed out that fears of large numbers of people adopting a
> Phoenician Unicode encoding would demonstrate the usefulness of the
> encoding. You responded that the same was true for Fraktur, even though
> there are no large numbers of people a
96 matches
Mail list logo
