Doug Ewell wrote:
Marco Cimarosti marco dot cimarosti at essetre dot it wrote:
He said that he didn't understand how this detail could help us but,
anyway, he obtained the child's name and address from the parent:
Daniel Zubeispiel
Hauptkirchestrasse, 26
Zürich, Switzerland
Is
I (Marco Cimarosti) wrote:
Of course. AFAIK, Zu Beispiel means e.g., for example.
Hauptkirchestrasse is a made-up road name meaning
cathedral street.
Zurich is the only real piece of the address.
But a native German speaker patiently explained, in a private message:
| If it's an example,
At 09:56 +0200 2002-09-30, Marco Cimarosti wrote:
Of course. AFAIK, Zu Beispiel means e.g., for example.
Recte Zum Beispiel.
--
Michael Everson * * Everson Typography * * http://www.evertype.com
48B Gleann na Carraige; Cill Fhionntain; Baile Átha Cliath 13; Éire
Telephone +353 86 807 9169 * *
At 17:14 -0700 2002-09-26, Kenneth Whistler wrote:
I am not suggesting this for bibliographic work, just wondering: for the
bibliographic work I feel that a new character of a COMBINING DOUBLE
INVERTED BREVE WITH DOT ABOVE might be a good solution.
Possibly. It is certainly a simple
[Still off-topic, but I'm hopeful that progress can be made, so am
continuing a little farther]
On 09/27/2002 10:26:36 AM William Overington wrote:
XML is the way to go.
Maybe, maybe not. The issue of U+003C being used to mean LESS-THAN SIGN
in
documents which mix ordinary text and markup
At 12:24 PM 9/27/2002 +0100, William Overington wrote:
You tell me which one is more
likely to result in productive work and adoption by others.
Likelihood of success and what actually happens are not the same thing. I
do not know which is more likely as I do not know of what has happened
At 12:23 PM 9/27/2002 +0100, William Overington wrote:
Are you perhaps trying to make a deduction by the fallacy of the
undistributed middle, along the following lines.
William's need is a markup system.
XML is a markup system.
William's need is XML.
I think what is being suggested is not
Marco Cimarosti marco dot cimarosti at essetre dot it wrote:
He said that he didn't understand how this detail could help us but,
anyway, he obtained the child's name and address from the parent:
Daniel Zubeispiel
Hauptkirchestrasse, 26
Zürich, Switzerland
Is this a pseudonym? I am
Michael Everson scripsit:
I don't see why you wouldn't just let the accent positioning=20
properties sort this out. In general if you are stacking accents the=20
higher ones appear above and centred over the lower ones.
Do they not?
I would expect later accents to be above earlier ones
Shawn Steele wrote to the [EMAIL PROTECTED] list, not directly to me, yet
began by writing.
Mr. Overington,
There is then a long document of very helpful information, for which I am
grateful.
Mr Steele then concludes with the following.
I hope that this example improves your understanding of
Peter Constable commented as follows.
On 09/26/2002 06:05:45 AM William Overington wrote:
Dallas is 6 hours behind England on the clock.
I'm going to refrain from commenting on anything beyond the markup issues
As you wish. Though did you stick to that even in the same sentence?
-- and
Peter Constable wrote as follows.
On 09/26/2002 03:42:16 AM William Overington wrote:
Well, it might have been 03:42:16 AM where you are, indeed it probably was,
as Dallas is six hours behind England on the clock, but I would not want
people to think that I write my posts in the middle of the
William Overington scripsit:
Well, it depends what one is trying to do. If one wishes to establish a
system whereby proprietary intellectual property rights exist, then a
proprietary coding can be a good idea.
That is the function of encryption.
XML is the way to go.
Maybe, maybe not.
[This is entirely off-topic.]
On 09/27/2002 06:24:27 AM William Overington wrote:
Yet what indication whatsoever do you have that I ignore what you write?
The fact that you have been given recommendations from several people on
this list not to invent new markup conventions but to take
On Friday, September 27, 2002, at 09:52 AM, [EMAIL PROTECTED]
wrote:
I doubt there's anyone on this list that always agrees with me
I think you're wrong, there, Peter. I *never* disagree with you. :-)
==
John H. Jenkins
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.tejat.net/
William Overington wrote:
Message catalogs are not new.
I had not heard the description Message catalog previously, so I can
search for that too.
I have previously searched under telegraphic code and language and
translation.
look for: software localization, message, catalog, resource
John H. Jenkins scripsit:
I think you're wrong, there, Peter. I *never* disagree with you. :-)
Hmm. Has anyone ever seen Peter and John together? :-)
--
John Cowan [EMAIL PROTECTED] www.ccil.org/~cowan www.reutershealth.com
In the sciences, we are now uniquely privileged to sit side
Tex Texin scripsit:
After a bit the new guy shouts out: 42! Dead silence. He asks his
neighbor what went wrong. He turns to him and says That one is not
funny..
Other punchlines I have heard:
(about a third party): Steve should know he can't handle Swedish dialect.
(after uproarious
At 04:26 PM 9/27/2002 +0100, William Overington wrote:
I had not heard the description Message catalog previously, so I can
search for that too.
I have previously searched under telegraphic code and language and
translation.
An email correspondent drew my attention to the following list of
Tex Texin wrote:
What's funny to me about this message, is a product message catalog I
was responsible for localizing had messages created by software
developers, such as (paraphrasing from memory):
The client is dead.
The client has been killed.
You killed the client.
Some of the
Peter Constable commented as follows.
On 09/25/2002 05:55:02 AM William Overington wrote:
For example, I am looking at using the following sequence so as to produce
a
special purpose key within documents.
U+2604 U+0302 U+20E3
Hopefully that sequence will be so unlikely to occur other than in
Marco Cimarosti asked about what key caps have to do with mark up or text
files.
My idea is as follows.
A document would contain a sequence such as follows.
U+2604 U+0302 U+20E3 12001 U+2460 London U+2604 U+0302 U+20E2
This would have a meaning such as follows.
It was a pleasure to welcome
On 09/26/2002 03:42:16 AM William Overington wrote:
On the one hand, you say
XML does not suit my specific need as far as I can tell.
But you also said
Documents with the code sequence are intended to be sent over the internet
as email, used as web pages and broadcast in multimedia
On 09/26/2002 06:05:45 AM William Overington wrote:
I'm going to refrain from commenting on anything beyond the markup issues
-- and I'm continuing with that only because it's an easy follow-on to what
I already wrote, even though there is every indication that the sensibility
of it will be
So that Peter's comments cannot be perceived as strictly Peter's view, I
am seconding them.
Message catalogs are not new.
A proprietary coding system is a bad idea.
XML is the way to go.
Failure to investigate the state of the art, (especially where google is
so effortless), means this idea is
Mr. Overington,
Peter didn't specifically mention that his suggestion is an example of XML, although
he alluded to that fact. As many people have mentioned before on this list, XML is a
more appropriate mechanism for many of your inventions, and it is also a standard.
One of the neatest
William Overington asked:
While on the topic, how would the following sequence be displayed please?
U+0074 U+0361 U+0073 ZWJ U+0307
Just like:
U+0074 U+0361 U+0073 U+0307
The sequence U+0073, ZWJ, U+0307 could request a ligature of the
s and the dot-above, but since it is unlikely that
Peter responded:
A document would contain a sequence such as follows.
U+2604 U+0302 U+20E3 12001 U+2460 London U+2604 U+0302 U+20E2
You could just as easily have used
S C=12001London/S
or
S C=12001 P1=London/
or even:
cometcircumflex messageId=12001London/cometcircumflex
if
The recent discussion on sequences has led me to have a look through the
various combining characters and I have found the following.
U+20E3 COMBINING ENCLOSING KEYCAP
It has occurred to me that the use of a sequence of a base character, then
one or more combining characters so as to produce a
William Overington WOverington at ngo dot globalnet dot co dot uk
wrote:
Also, I have noticed that in the document U02D0.pdf
(actually U20D0.pdf)
that U+20E4 is
shown, in the listing, in magenta whereas U+20DF is shown in black.
Could someone say what significance the magenta colouring in
William Overington wrote:
The recent discussion on sequences has led me to have a look
through the various combining characters and I have found
the following.
U+20E3 COMBINING ENCLOSING KEYCAP
It has occurred to me that the use of a sequence of a base
character, then one or more
On 09/20/2002 07:07:30 PM Kenneth Whistler wrote:
Well, yes, it would be anomalous, which is why it would require
somebody to go to the trouble to make a special ligation table
entry for it.
But what longer-term problems are you talking about?
I'm saying that *if* there is a need for digitial
Charles Cox suggested:
Might there be a case for defining an invisible combining enclosing mark
(ICEM), which is otherwise identical to the enclosing circle? Then, if I've
understood the conventions correctly the sequence:
U+0074 U+034F U+0073 ICEM U+0311 U+0307 would give ts with a
On 09/20/2002 04:44:46 PM Kenneth Whistler wrote:
This stuff *can* all be handled with appropriately designed
ligations in fonts, so there are options for display:
U+0074, U+0361, U+0073, U+0307
==
maps via ligation table to:
{t-s-tie-ligature-with-dot-above} glyph
I would consider
Peter said:
This stuff *can* all be handled with appropriately designed
ligations in fonts, so there are options for display:
U+0074, U+0361, U+0073, U+0307
==
maps via ligation table to:
{t-s-tie-ligature-with-dot-above} glyph
I would consider this an anomolous rendering.
]
Actually, this matter to which I was intending to refer was as follows,
being more general than just the romanization of Cyrillic characters.
quote
It seems to me that this matter of sequences of combining characters being
used to give glyphs where different meanings are needed other than just
locally
+0055 U+0313 mentioned above,
and possibly others, will be needed for the Byzantine legal codes.
It seems to me that this matter of sequences of combining characters being
used to give glyphs where different meanings are needed other than just
locally and that glyphs for such meanings are only
William Overington wrote:
Regarding Ken's response to the Byzantine legal codes matter, it would
appear possible that the way that the ts ligature with a dot above for
romanization of Cyrillic could be represented in Unicode
would be by the following sequence.
t U+FE20 s U+FE21 U+0307
I
On 09/18/2002 03:48:41 AM Marco Cimarosti wrote:
Using the COMBINING DOUBLE INVERTED BREVE doesn't make things much better:
t U+0361 s U+0307
Still, U+0361 only applies to t,
I'm not sure why you say that. t, 0361, s should render with the
inverted breve spanning both the t and the s.
William Overington asked:
In the discussion about romanization of Cyrillic ligatures I asked how one
expresses in Unicode the ts ligature with a dot above.
Regarding Ken's response to the Byzantine legal codes matter, it would
appear possible that the way that the ts ligature with a dot
The ALA-LC conventions are not the only alternatives available for
representation of Abkhaz and/or Khanty/Mansi data in romanization.
In fact, you can find such data on the web using alternative
romanizations. So it isn't as if the current gap in figuring out
precisely how, in Unicode, to
The ALA-LC conventions are not the only alternatives available for
representation of Abkhaz and/or Khanty/Mansi data in romanization.
In fact, you can find such data on the web using alternative
romanizations. So it isn't as if the current gap in figuring out
precisely how, in Unicode, to
42 matches
Mail list logo
