Re: Ugaritic Affiliations

On Sun, 09 Sep 2007 14:22:59 -0700, "Peter T. Daniels"
<grammatim@xxxxxxxxxxx> wrote in
<news:1189372979.359412.144370@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
in sci.lang:

On Sep 9, 3:06 pm, "Richard Wordingham" <jrw0...@xxxxxxxxxxx> wrote:

"Peter T. Daniels" <gramma...@xxxxxxxxxxx> wrote:

On Sep 8, 6:07 pm, "Richard Wordingham" <jrw0...@xxxxxxxxxxx> wrote:

"Peter T. Daniels" <gramma...@xxxxxxxxxxx> wrote:

On Sep 8, 9:17 am, "Richard Wordingham"
<jrw0...@xxxxxxxxxxx> wrote:

Unicode documents are a pretty reliable source of ISO
10646 character names, which can be useful when
there's uncertainty as to which character is meant.

Being a character list rather than a glyph list, it
does have the disadvantage that glyph variants are not
covered, so that for neo-Assyrian, for example, one
has to use to supplementary tables, such as the
alphabetically-ordered one at
http://www.sumerisches-glossar.de/download/SignListNeoA
ssyrian.pdf.

??? Who in their right mind would even _think_ of
looking in Unicode for reliable information on
cuneiform writing?

No one suggested doing anything of the kind. Richard merely
pointed out that ISO 10646 provides standardized *names* for
characters.

It's the natural place to look for the standard
identification of a character, regardless of script. It
has the advantage of being available to anyone with
unrestricted internet access.

That's like saying wikipedia has the advantage of being
available to anyone with unrestricted internet access.

You're missing the point. Unicode *does* in fact provide
standardized names that can be used to identify a character
unambiguously, and these names *are* readily available.
It's much easier to give one of these names than to try to
describe a character's shape, and interpreting the name
doesn't require access to any specialized sources (like WWS,
for instance).

Unicode is very much a case of GIGO.

It appears that you know even less about Unicode than you do
about Wikipedia. In this case you're definitely letting the
best be the enemy of the good.

[...]

Brian
.

Relevant Pages

  • Re: VB - Ascii to Unicode and then Unicode to UTF-8 conversion (Very desperate!!)
    ... Latin together) then you have to use a Unicode column type. ... AscW returns the real Unicode character ... for Chinese characters, ... then the next thing to worry about is your CSV file. ...
    (microsoft.public.vb.general.discussion)
  • Re: Unicode Support
    ... if two Unicode strings are the same? ... UTF-16 is basically telling everyone "ok we all got to start ... character, and will likely support *both* endians. ... UTF-8 encodings are also easy to learn to ...
    (alt.lang.asm)
  • Re: Determining if a string is Unicode
    ... there's nothing magic about Unicode. ... where each character occupies 2 bytes, as opposed to a Single-Byte Character ... You could load up a string with rubbish, ... > INF file like so: ...
    (microsoft.public.vb.general.discussion)
  • Re: KANJD212
    ... >>Who decides the factors and what are their criteria, Unicode? ... But once a character is defined/get a codepoint in Unicode it ... standard modifies the codepoint of the kanji to a totally new ... I can use a code like JIS X0208 along with a font ...
    (sci.lang.japan)
  • Re: Enhanced Unicode support for "Go" tools
    ... the point to remember is that UNICODE is a _character ... It's the fonts, the OS and the application which work together ... society for the protection of French from English ...
    (alt.lang.asm)