On Sat, Jun 18, 2011 at 14:09, Gerrit wrote:
> I thought of romanization which is specific to the language the surrounding
> text is written in - e.g. French or German. And this is not so much the case
> for Chinese or Japanese (except for some words: Beijing in English but
> Peking in German). In
On Sun, 19 Jun 2011, Tobias Schoel wrote:
> Am I the OP? (I don't know that abbreviation and therefore I am confused.) But
Yes. It's an old Usenet abbreviation standing for "Original Poster."
--
Matthew Skala
msk...@ansuz.sooke.bc.ca People before principles.
http://ansuz.sooke.b
Hi,
there are some commercial fonts which claim to have a arabic->roman
feature (may be reduced to the numbers up to 5000 or so) e.g. P22
Operina Pro.
Btw: Arabic->Roman is probably much easier to implement than the
inverse. I don't know font details, but from what I have read, it could
be
It seems to me (having worked with OpenType fonts for some years) that
while it might be possible to make an Arabic-->Roman converter at the
font level, that's going to be one of the most inefficient possible ways
to handle it. With OT you can make a set of rules that says
Here's a 1 followed
Hello Enrico,
On 20/06/2011, at 5:42 AM, enrico.grego...@univr.it wrote:
> What the OP wants is that "CXV" is stored as a unique glyph representing 115.
> Maybe this can be done by reserving, say, five thousand slots in Unicode to
> contain the numbers from 1 to 5000 in Roman form that are built
On Sun, 19 Jun 2011, enrico.grego...@univr.it wrote:
> What the OP wants is that "CXV" is stored as a unique glyph representing 115.
> Maybe this can be done by reserving, say, five thousand slots in Unicode to
> contain the numbers from 1 to 5000 in Roman form that are built from the basic
If you
On Sun, 19 Jun 2011, Tobias Schoel wrote:
> that's a good answer. is there such an opentype feature / fonts supporting it?
I don't know of a font that does Arabic->Roman numeral translation as
glyph substitution while preserving the original Arabic code points. I'm
considering building an Arabic-
> enrico.grego...@univr.it wrote:
>
> > When you highlight characters in a PDF and copy them you get the codes and
> > all that it's attached to them. The problem with Roman numerals is that a
> > "digit" has different meanings depending on the context. The "C" in "CXV"
> > means 1, but in "CMXV"
Arthur Reutenauer wrote:
I'm not entirely convinced that I agree. I would argue that the "C"
of "CXV" means "100", not "1"; in "CMXV" it means "subtract 100".
At least, that's what we were taught at school !
Yes, but if you want to transcribe into Arabic numerals you have to
translate "C
2011/6/19 Philip TAYLOR (Webmaster, Ret'd) :
> What is a "kill file" ? Another platform-specific feature, I suppose !
http://lmgtfy.com/?q=kill+file&l=1
--
Subscriptions, Archive, and List information, etc.:
http://tug.org/mailman/listinfo/xete
> I'm not entirely convinced that I agree. I would argue that the "C"
> of "CXV" means "100", not "1"; in "CMXV" it means "subtract 100".
> At least, that's what we were taught at school !
Yes, but if you want to transcribe into Arabic numerals you have to
translate "C" as "1" in the first case
hi,
that's a good answer. is there such an opentype feature / fonts
supporting it?
bye
Toscho
Am 19.06.2011 15:33, schrieb msk...@ansuz.sooke.bc.ca:
On Sun, 19 Jun 2011, Tobias Schoel wrote:
if I understand correctly, that way the output still shows the letters or the
deprecated unicode co
enrico.grego...@univr.it wrote:
When you highlight characters in a PDF and copy them you get the codes and
all that it's attached to them. The problem with Roman numerals is that a
"digit" has different meanings depending on the context. The "C" in "CXV"
means 1, but in "CMXV" it means nothing
> Hi,
>
> if I understand correctly, that way the output still shows the letters
> or the deprecated unicode codepoints. It should be analog to medieval /
> lowercase numbers. E.g. it's still the number 123 it only uses different
> glyphs. So when I copypaste it, it shows the number 123 and not
Alan Munn wrote:
This is a useful and friendly list. Let's keep it that way.
I had no intention of doing otherwise. I was asking for
additional information, not levelling criticism.
> Rather than entering into a long discussion with Pete about this, perhaps you
could have verified your in
On Jun 19, 2011, at 7:53 AM, Philip TAYLOR (Webmaster, Ret'd) wrote:
>
> Peter Dyballa wrote:
>
>> You could specify the renderer engine! Fontspec allows
>>
>> \fontspec[Renderer=AAT]{font}
>
> Is this meaningfully true for all platforms ? One of the
> few downsides to XeTeX is that sometimes
Am 19.06.2011 um 15:58 schrieb Philip TAYLOR (Webmaster, Ret'd):
I am not complaining : I am asking for precision, which
is another matter entirely.
So, here is precision: AAT is a proprietary Mac OS X font technology
from Apple (maybe doomed to die). It started as QuickDraw GX, on which
On Jun 19, 2011, at 8:58 AM, Philip TAYLOR (Webmaster, Ret'd) wrote:
>
>
> Peter Dyballa wrote:
>>
>> Am 19.06.2011 um 15:14 schrieb Philip TAYLOR (Webmaster, Ret'd):
>>
>>> Yes, but your mail will be read by others (such as myself)
>>> who are unaware of either of these facts, and will then
Peter Dyballa wrote:
Am 19.06.2011 um 15:14 schrieb Philip TAYLOR (Webmaster, Ret'd):
Yes, but your mail will be read by others (such as myself)
who are unaware of either of these facts, and will then be
misled into believing that it should work in their platform.
The term "AAT" stands for
Am 19.06.2011 um 15:14 schrieb Philip TAYLOR (Webmaster, Ret'd):
Yes, but your mail will be read by others (such as myself)
who are unaware of either of these facts, and will then be
misled into believing that it should work in their platform.
The term "AAT" stands for "Apple Advanced Typogra
On Sun, 19 Jun 2011, Tobias Schoel wrote:
> if I understand correctly, that way the output still shows the letters or the
> deprecated unicode codepoints. It should be analog to medieval / lowercase
> numbers. E.g. it's still the number 123 it only uses different glyphs. So when
> I copypaste it, i
Hi,
if I understand correctly, that way the output still shows the letters
or the deprecated unicode codepoints. It should be analog to medieval /
lowercase numbers. E.g. it's still the number 123 it only uses different
glyphs. So when I copypaste it, it shows the number 123 and not cxxiii.
Peter Dyballa wrote:
Am 19.06.2011 um 13:53 schrieb Philip TAYLOR (Webmaster, Ret'd):
Is this meaningfully true for all platforms ?
Of course not. But Blake used Apple Mail to send his message and he also
mentions Mac OS X as the OS he uses, where his problems occur. So I
tried to use my b
On Jun 19, 2011, at 7:55 AM, Philip TAYLOR (Webmaster, Ret'd) wrote:
>
>
> Herbert Schulz wrote:
>
>>> Peter Dyballa wrote:
>>>
You could specify the renderer engine! Fontspec allows
\fontspec[Renderer=AAT]{font}
>>>
>>> Is this meaningfully true for all platforms ? One of t
Am 19.06.2011 um 13:53 schrieb Philip TAYLOR (Webmaster, Ret'd):
Is this meaningfully true for all platforms ?
Of course not. But Blake used Apple Mail to send his message and he
also mentions Mac OS X as the OS he uses, where his problems occur. So
I tried to use my brain and mentioned t
Herbert Schulz wrote:
Peter Dyballa wrote:
You could specify the renderer engine! Fontspec allows
\fontspec[Renderer=AAT]{font}
Is this meaningfully true for all platforms ? One of the
few downsides to XeTeX is that sometimes a feature is
platform-dependent yet the documentation and/or c
On Jun 19, 2011, at 6:53 AM, Philip TAYLOR (Webmaster, Ret'd) wrote:
>
>
> Peter Dyballa wrote:
>
>> You could specify the renderer engine! Fontspec allows
>>
>> \fontspec[Renderer=AAT]{font}
>
> Is this meaningfully true for all platforms ? One of the
> few downsides to XeTeX is that somet
Peter Dyballa wrote:
You could specify the renderer engine! Fontspec allows
\fontspec[Renderer=AAT]{font}
Is this meaningfully true for all platforms ? One of the
few downsides to XeTeX is that sometimes a feature is
platform-dependent yet the documentation and/or correspondence
never ment
Am 18.06.2011 um 23:20 schrieb Blake Wentworth:
I would be delighted to know where the source of the initial problem
lies
You could specify the renderer engine! Fontspec allows
\fontspec[Renderer=AAT]{font}
(other options are ICU, usable for most fonts, and Graphite, usable
for j
Greetings,
I have recently been using Tamil fonts sold by the font developer Xenotype
Technologies, which are conversions of OpenType fonts to AAT. The aim was to
allow me to use Tamil fonts other than the default InaiMathi font with Mac OS
X's keyboard driver for Tamil, Murasu Anjal. Initia
30 matches
Mail list logo
