implementing Unicode.
My recommendation is simply to ignore WG2 and act as if it doesn't
exist. It already might as well not, and with its policies is only
likely to become more and more irrelevant.
JH
--
John Hudson
Tiro Typeworks Ltdwww.tiro.com
Salish Sea, BCt...@tir
Christopher Fynn wrote:
OpenType is an openly available specification for fonts which anyone
can use without paying a licence to adobe or microsoft who maintain
the specification
While Microsoft and Adobe maintain the OT specification, it should be
noted that the OT spec is in synch with the
Mahesh T. Pai wrote
> PUA isn't necessary, and a font technology that handles elements of
> complex script shaping by referencing PUAs isn't fundamentally any
> different from one that uses glyph names or another identifier and
> leaves the glyph unencoded.
Does one exist? Does it work? (
Mahesh T. Pai wrote:
It is another matter that no font actually uses a non-opentype layout,
which basically requires putting the "non-encoded" glyphs in the
Private Use Area (PUA), and then call the glyphs by a name.
PUA isn't necessary, and a font technology that handles elements of
complex
Philippe, I'll need to think about this some more and try to get a
better grasp of what you're suggesting. But some immediate thoughts come
to mind:
If BiDi is to be applied to shaped glyph strings, surely that means
needing to step backwards through the processing that arrived at those
shape
Philippe Verdy wrote:
Rereading closely the OpenType spec...
I suggest you read also the script-specific OT layout specifications.
http://www.microsoft.com/typography/SpecificationsOverview.mspx
You'll note, for example, that the Arabic font spec doesn't even mention
BiDi, because it is ass
Behdad Esfahbod wrote:
I can see the advantages of such an approach -- performing GSUB prior to BiDi
would enable cross-directional contextual substitutions, which are currently
impossible -- but the existing model in which BiDi is applied to characters
*not glyphs* isn't likely to change. Switc
Philippe Verdy wrote:
The computing order of features should not then be:
- BiDi algorithm for reordering grapheme clusters
- font search and font fallback (using cmap)
- GSUB (lookups of ligatures or discretionary glyph variants)
- GPOS
but really:
- font lookup and font fallback (u
Shriramana Sharma wrote:
I was just noting
that the glyph tables themselves don't *use* the actual codepoints of
the characters getting ligated (while they *refer* to them).
Characters are mapped to glyph IDs in the font cmap tables.
Glyph IDs are mapped to other glyph IDs (one-to-one, one-t
Shriramana Sharma wrote:
The font tables themselves contain only ASCII characters I presume.
OpenType Layout tables use Glyph IDs. OTL development tools typically
use glyph names, which may be particular to the tool or the same names
used in the post or CFF tables.
OTL tables work on glyph
Petr Tomasek wrote:
Not in Hebrew. The only common ligature is the aleph_lamed, a
post-classical import from Judaeo-Arabic.
Not true. See:
Collete Sirat. Hebrew Manuscripts of the Middle Ages. Cambridge University
Press 2002,
fig. 114 (p. 176) or fig. 127 (p. 189) or fig. 134 (p. 193).
I w
Jonathan Rosenne wrote:
People do all kinds of fancy things. I guess old manuscripts contain many
ligatures...
Not in Hebrew. The only common ligature is the aleph_lamed, a
post-classical import from Judaeo-Arabic.
JH
--
Tiro Typeworkswww.tiro.com
Gulf Islands, BC t...@tiro.
testing. The most recent release version of Uniscribe is that
which ships with Office 2003.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The peasant of the Garonne, by Jacques Maritain
The land of Ulro, by Czeslaw Milosz
letter? In the case of Zarqa, it's clearly a combining mark on the
letter, based on other accents, printing, and general perception through
the years. But in general?)
I don't know, I'm not a generalist :)
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[
sets) fonts that worked only in the private
applications for which they were made.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Peasant of the Garonne, by Jacques Maritain
Art and faith, by Jacques Maritain & Jean Cocteau
Dif
in.
It really is a better idea to use the decomposed forms, and to allow text representation
to be handled at the glyph level.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Peasant of the Garonne, by Jacques Maritain
Art and faith,
ot pointing and thus not combining marks (though the
vowel points of course are combining marks). They appear to be used
more as punctuation than as letter-diacriticals.
Do you mean that they are spacing characters?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTE
s to be freely available, you have to find some way to pay
for their development, e.g. the model of the SBL Font Foundation, which is raising funds
from partner organisations to pay for free fonts for Biblical scholarship.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL
that text.
By all means recommend that for most purposes ketiv and qere should be separately encoded:
there are lots of good reasons to do so. But don't ignore the need to correctly display
the merged forms, which is a textual problem requiring a solution that is at least in part
charact
they 'probably
need' them. An Apple AAT (GX) font also includes layout tables, although using a different
approach than OT.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Peasant of the Garonne, by Jacques Maritain
Art
but proprietary.
It doesn't claim to be a 'standard': it is a font format that happens to be more widely
supported than other font formats.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Peasant of the Garonne, by
ing
but proprietary.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Peasant of the Garonne, by Jacques Maritain
Art and faith, by Jacques Maritain & Jean Cocteau
Difficulites, by Ronald Knox & Arnold Lunn
font foundry?
No. Monotype grabbed the OpenType domain name (and a lot of other type
related domains).
The OpenType specification and other documentation is all at the MS Typography
site:
http://www.microsoft.com/typography
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC
k of when they hear 'OpenType', is supported to
different levels in different system and application mixes, and is also likely to enjoy
more support for some writing systems than others.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently read
discussion of Phoenician, so that
those who are interested may discuss the encoding and implementation issues without
deluging those who are less interested. One may subscribe to this list by sending an
e-mail to:
[EMAIL PROTECTED]
John Hudson (who is not subscribed to that list)
--
Tiro
Mark E. Shoulson wrote:
Well, that's the difference under discussion. The "plain text" would
seem to be either the qere or the ketiv (but not the combined "blended"
form), since each of those is somewhat sensible.
Is there some place in the standard where it says text must be sensible?
JH
--
Ti
tions as to how things might be
handled in either encoding or display. So if you think merged Ketiv/Qere forms should be
handled by markup, perhaps you can explain how, so that I might better understand. Thank you.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTE
page as a
marginal note be considered any differently from text anywhere else *in its encoding*? Are
you suggesting that Unicode is only relevant to ... what? totally unformatted text in a
text editor?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Current
ifferent for Hebrew?
I'm just trying to understand the basis of your insistence that traditional Ketiv/Qere
combinations are not plain text. I can understand how and why one might implement them not
as plain text, but this is not the same as determining, a priori, that they are not an
tradition of
writing them in combination. Saying that people should cease writing them as they have
been written, and write them only separately doesn't seem to me to be much of a solution.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently re
single-storey
lowercase a, such as Futura.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Mass in slow motion, by Ronald Knox
Hebrew manuscripts of the Middle Ages, by Colette Sirat
tree:
http://www.amazon.com/exec/obidos/tg/detail/-/0300013140
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Seven Storey Mountain, by Thomas Merton
Hebrew manuscripts of the Middle Ages, by Colette Sirat
orm and
typographic representation. Furthermore, it is a symbol specified by, recognised by, and
encoded by national standards bodies. Unsurprisingly, if a government comes along and says
'We have this legal symbol that means X and we have a need to use it in plain text', that
symb
whether or not the Creative Commons logo is a glyph
variant of the Copyleft logo. :)
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
The Seven Storey Mountain, by Thomas Merton
Hebrew manuscripts of the Middle Ages, by Colette Sirat
ouble-diacritic must be adjusted so that it is above the *taller*
of the preceding and following combining sequence. AFAIK, such logic isn't
feasible in OpenType.
You could handle it fairly easily by contextually substituting a glyph variant of the
double-diacritic at a different height.
J
ously like one of the recognised forms of the Ypsilon in
non-archaic Greek.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Colette Sirat
nsidered
individual scripts outside of Unicode isn't very relevant to this usage. Indeed, Unicode
might have avoided all this debate by not using the term script at all.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Pet
#x27;t strike me as a significant problem.
Encoding half a dozen of these 'nodes' might be, because with each additional structurally
identical script the number of choices and likely confusion increase.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTE
of enumerated entities. I like that :)
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Colette Sirat
that the encoding of Phoenician, for
example, is eventually going to be determined by the plain text needs or desires of
specific users. I'm simply encouraging people to think about the Unicode notion of script
in these terms, as I think it will save us a lot of wasted bandwidth, energy and
users consider a single script, whether users in general opt to make the distinction in
plain text or not, by using the separate character collections or unifying text in a
single character collection and making the distinction at a higher level. I'm beginning to
think that our time would be
e
to see some real world situations arising from work that someone is doing with ancient
semitic writing in which there is a need for plain-text distinction of two or more ancient
semitic scripts.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currentl
nct is
unlikely to get us anywhere. The identity very much depends on the perspective of the
observer.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Colette Sirat
e. of a linear continuum with clearly identifiable chronological or
cultural script instances. Dean has, convincingly I think, presented examples of
overlapping of use of such 'nodes' among ancient communities, making it harder to
distinguish them from within the continuum.
John Hud
obstacle to the argument going full circle yet again. Hebrew and
Palaeo-Hebrew letters occur side-by-side on some modern Israeli coins also. See the
photography near the bottom of this Typophile discussion:
http://www.typophile.com/forums/messages/4101/27209.html
John Hudson
--
very short mimes of the snow gods do not wish
at all that the very great burden of distributing the
wine of the walls will be lightened in their lifetime.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter
Both sides has four generals: two 'gold' and two 'silver'. The gold and silver
generals differ from each other, but each side's pieces are entirely identical.
By the way, if any Unicoders play shogi, I could bring my travel set next time I come to
the confer
ing ones, since more contentious questions tend to be
raised by such writing systems.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Colette Sirat
scripts have varying shaping
behaviour, not all of which is easily addressable at the glyph level. There is a net
benefit to text processing and display in not unifying their encoding.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
a *plain-text* need for this stuff? At what point is it
more practical to say 'use a graphic'?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscri
oing to get us very far.
Whether Phoenician is encoded or not, I sincerely hope that the outcome of this process is
a better *mutual* understanding among the makers and users of Unicode.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Libronic use Unicode encoding for their electronic BHS edition (because it
provides greater interchangeability), they maintain an MCW encoded text as their master
source. So much for the 'universal' character set...
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL
stinction of 'Phoenician' from Hebrew and, presumably, from some other forms of ancient
Near Eastern writing. Patrick has, today, noted the existence of an inscription that
includes both Punic and Neo-Punic forms: is this a distinction that someone might have a
'need' to
what
reasons are given.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Colette Sirat
ecialist perspective, with that generalist history, they deserve better
than 'Of course it is a separate script, I have a lot of books that say it is'.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
W
istinction of 'Phoenician' and Hebrew, yet
more complexity and sophistication will be required to encode, search and study ancient
texts. Frankly, I don't blame people for asking whether that distinction is worth the trouble.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouve
s all represent the same 22 abstract characters.
The Unicode Standard encodes abstract characters.
Ergo, only one set of codepoints is required to encode the
22-letter semitic writing systems.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently re
hat they acknowledge that particular styles of writing are or are not
appropriate for religious texts is neither surprising nor relevant, as the same
distinctions are made between ktiva merubaat and stam.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTE
for why anyone would need to make such a distinction?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Colette Sirat
t much difference between transliteration and encoding in practice.
I don't think the history of writing systems is going to help us here. There
is no disagreement about the facts, just about their interpretation.
Thank you, Jony. This is needed to be said and you put it very well.
John Hudson
--
Tiro
to identify the user communities that believe they have a need to make a
plain-text distinction, and you need to convince them that they don't really need it after
all.
Be prepared, however, for the possibility that the expressed need may turn out to be
legitimate.
John Hudson
--
Tiro Type
only pointing out that you are failing to
achieve it with your current strategy.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by William Dalrymple
Hebrew manuscripts of the Middle Ages, by Co
s proposal should be
accepted or rejected, which means that 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.
John Hudson
of a particular set of
characters does not mean that they have to be used to encode particular texts or languages.
John Hudson
is so daft.
My question, again, is whether there is a need for the plain text distinction in the first
place?
John Hudson
ith Hebrew *because no
decision has been made by the UTC*. Lack of a decision neither implies unification or
non-unification. Phoenician is in the box with Schroedinger's cat.
John Hudson
reason, I don't
automatically accept the argument, made by Michael earlier today, that 'There is a
requirement for distinction for X in plain-text'.
On what basis do we decide that X is necessary in plain-text while Y should be done with
mark-up or some other 'higher level protocol'?
John Hudson
, Moabite, Palaeo-Hebrew, etc. -- variations that are not even cleanly
defined by language usage -- with such sequences?
Some people seem keen on variation selectors in the same way that others are keen on PUA:
as a catch-all solution to non-existent problems.
John Hudson
distinction in plain-text, while the question of whether there is a requirement to use
plain-text in the first place gets asked less often.*
*Except by Jony, who is always encouraging us to use markup to make distinctions.
John Hudson
e norm for writing a language, rather than
as simply one stylistic possibility.
John Hudson
Jony Rosenne wrote:
Mozilla's main value is for non-Windows platforms.
And for people who are unimpressed by Outlook's security track record.
JH
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
White Mughals, by Willia
ve raised these
specific issues about document encoding: have you considered these? do you think they are
a problem? do you still want what you said you wanted?'
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Pe
in the program directory and the appropriate OpenType fonts installed, you
should be able to enjoy exactly the same text rendering in Thunderbird as in Word.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
Currently reading:
Typespaces, by Peter Burnhill
Wh
African languages have been quite extensively
discussed on that mailing list, and there is a higher number of African participants than
on the Unicode list. For details, see http://www.bisharat.net/ and, for mailing list
subscription, http://lists.kabissa.org/mailman/listinfo/a12n-collaboration
John
changed in order to overcome the shortcoming of particular software developers
is clearly backwards.
But I'm still not sure exactly what you are suggesting should be done.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says
R.C. Bakhuizen van den Brink [Rein] wrote:
How well does low-budget Eudora support Unicode?
Eudora does not currently support Unicode, but the very excellent and *free* Mozilla
Thunderbird e-mail program does. See: http://www.mozilla.org/products/thunderbird/
John Hudson
--
Tiro Typeworks
so we can avoid this kind of bandwidth-hogging
debate in future.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I succeed so
lock
is misnamed. Even if one accepts that 'Phoenician' should be separately encoded, the
Hebrew block should have been called 'Aramaic' :)
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is
rom
those which you want to encode, if 1:1 correspondence is not sufficient grounds for
unification but visual dissimilarity is grounds for disunification?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he
guages, and
prepared to respond to queries or objections regarding specific characters.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I
nisms. The question is
whether the distinction is necessary in plain text.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I
rms are readable by modern Jews, or whether
they may be used in religious texts -- and I note that you are not suggesting that STAM
should be separately encoded, even though it is the *only* style approved for use in Torah
scrolls --: the issue is how ancient texts should be encoded.
John Hudson
--
er doesn't does not seem a compelling reason not to unify them.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I succ
(and trigraph and tetragraph) encoding several times, and generally confusion stems from
not understanding that higher level protocols are expected to handle rendering and things
like sorting and spellchecking.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I
Michael Everson wrote:
No Georgian can read Nuskhuri without a key. I maintain that no Hebrew
reader can read Phoenician without a key. I maintain that it is
completely unacceptable to represent Yiddish text in a Phoenician font
and have anyone recognize it at all.
But no one is going to do that
reasons to stop encoding historic scripts. They may,
however, be taken into account when deciding whether or not to encode an historic script
that at least some people consider to be already encoded.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play
existing 'Hebrew' characters? If so, what are
these objections?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to w
adequately for inclusion in proposals.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I succeed sometimes
In making him win.
- Charles Peguy
he is unlikely to consider whether his needs are better met with new Phoenician
characters or existing Hebrew ones, especially if the possibility of using the latter is
not presented to him.
That said, I am very glad that Ms Anderson's further questions encourage users to review
the Phoen
le
with Hebrew characters is transliteration. You can't proceed past that argument simply by
restating your premise.
I'm not saying that I agree wholeheartedly with the contra-argument, but don't think you
can duck the argument by begging the question.
John Hudson
--
Tiro Typewor
ms to have
been wrong in this: many of the people most likely to be working with old Canaanite texts
in various languages -- i.e. semiticists -- seem to consider Phoenician anything but
simple and obvious.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I of
/iso15924-codes.html the 4-letter
script codes are shown capitalised, e.g. Arab not arab, Armn not armn, etc.. Is this
intentional? Should the codes always be capitalised? Does it matter if they are not?
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often
of writing
systems calls the script 'Phoenician' because the Greeks derived their alphabet from trade
contact with the Phoenicians. As should be obvious from recent debate, semiticists look at
the old Canaanite writing systems in a different way.
John Hudson
--
Tiro Typeworkswww.ti
cian style with appropriate glyphs.
I'm not saying that this is necessarily the best encoding for the Mesha Stele, but I'm
certainly not convinced that there is anything improper about it, or that having a
separate encoding for those glyphs would be more proper.
John Hudson
--
Tiro Type
Ken suggested, how to apportion the halves of the baby,
but where to make the cut.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I
for those users for whom the distinction is not only untidy
but, in their work, traditionally non-existent.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot,
Hebrew and the common North Semitic script as distinct.
John Hudson
--
Tiro Typeworkswww.tiro.com
Vancouver, BC[EMAIL PROTECTED]
I often play against man, God says, but it is he who wants
to lose, the idiot, and it is I who want him to win.
And I succeed sometimes
In
credentials or knowledge --, but all I'm personally questioning is the one
sentence in which he says the new Phoenician characters should be used used for
Palaeo-Hebrew. I'm not sure that this is the best recommendation to make to the people who
actually work with Palaeo-Hebrew.
John
larger body of Hebrew
text in which such experts are likely to be interested. But your proposal specifically
states that the 'Phoenician' characters should be used to encode Palaeo-Hebrew, as if
somehow Hebrew and Hebrew are different languages when they look different.
John Hudson
--
Tiro
Michael Everson wrote:
At 19:10 -0700 2004-04-29, John Hudson wrote:
Michael, Peter is not talking about the Phoenician language being
represented in the Hebrew script, he is talking about the common
practice of semiticists to *encode* the Phoenician script using Hebrew
codepoints. The
1 - 100 of 602 matches
Mail list logo
