On Fri, 12 Oct 2001, Carl W. Brown wrote:
> If I recall, it was distributed as a patch to Arabic Win98 so if you were
> inclined to buy a copy of Windows in a country with no intellectual property
> laws you co then apply the patch which made minor modifications to add the
> LCID and make changes
On Fri, 12 Oct 2001, Carl W. Brown wrote:
> I was told that there was a special (semi official) version of Win98 that
> added 4 missing letters in CP1256 by replacing Latin letters to create
> CP1256mod. It used LCID 0826.
Semi official? You mean in Microsoft's Persian Windows 3.1?
roozbeh
Lars,
> Actually, these definitions are both Daniels'. The one you attribute
> to me appears on page xxxix (first page of "Abbreviations,
> Conventions, and Definitions") of Bright and Daniels.
Hmm. I missed that. I guess Daniels and Bright decided not to
take a definitional approach to their di
Lars,
> * Kenneth Whistler (in an earlier posting)
> |
> | 2. Script B is a de novo design influenced strongly by Script A.
> |
> | 3. Script B borrowed formal and/or functional characteristics of
> | Script A.
>
> Unless I am missing something both 2. and 3. involves a cloning of
> concepts,
* Kenneth Whistler
|
| My greater issue with your type classification has to do with my
| disagreement about how you have defined some of the types.
You've certainly exposed my ignorance here. Before this thread started
I was dissatisfied with my typology on two counts:
a) I did not understan
* Kenneth Whistler (in an earlier posting)
|
| 2. Script B is a de novo design influenced strongly by Script A.
|
| 3. Script B borrowed formal and/or functional characteristics of
| Script A.
* Kenneth Whistler
|
| Yes. Xi Xia is a good example of a de novo design influenced strongly
| by Han
I recall something of the sort when we released Win98 for a specific non-US locale, although I can't remember the details. MS released the tier 2 and later locale versions after the initial tier 1 release of US, DE, JA, TC, SC, and KO. Many contained last minute bug fixes or locale specific patc
MickKa,
If I recall, it was distributed as a patch to Arabic Win98 so if you were
inclined to buy a copy of Windows in a country with no intellectual property
laws you co then apply the patch which made minor modifications to add the
LCID and make changes to the Unicode to code page conversion an
Probably mistaken -- or a "pirate" version (pirate is in quotes there since
legally it is not pirating to copy software, modify it, and sell it as your
own in certain countries).
MichKa
Michael Kaplan
Trigeminal Software, Inc.
http://www.trigeminal.com/
- Original Message -
From: "Carl
Roozbeh,
I was told that there was a special (semi official) version of Win98 that
added 4 missing letters in CP1256 by replacing Latin letters to create
CP1256mod. It used LCID 0826.
Carl
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Roozbeh P
From: "Roozbeh Pournader" <[EMAIL PROTECTED]>
> CP1256 has never supported FARSI YEH.
> No it's not. Persian locale is only avaiable on Windows 2000 and XP, which
> are Unicode based.
Unfortunately, it is a bit more complicated then that.
GetLocaleInfo/LOCALE_IDEFAULTANSICODEPAGE for Farsi doe
On Sat, 29 Sep 2001, Miikka-Markus Alhonen wrote:
> > alternate double marks (Fathatan, Kasratan, Dammatan)
> > and some other marks which are used in official Korans of the Islamic
> > countries scribed by Osman Taha; and finally the smaller variants of
> > Fatha, Kasra, and Damma introduced by
In a message dated 2001-10-11 10:50:09 Pacific Daylight Time, [EMAIL PROTECTED]
writes:
> Why does Roozbeh think this is 'the worst thing in Unicode'?
Probably because it seems so ugly and hackish: 3 formatting characters
required to provide shaping information for 2 graphic characters. "Turn
On Thu, 11 Oct 2001, John Hudson wrote:
> Why does Roozbeh think this is 'the worst thing in Unicode'?
Peter answered that. Three characters just for asking not to ligate? It's
neither beautiful nor clean. Standards should not recommend hacks of
themselves...
(Please note that I am against enco
Bob's completely right. CP1256 is not adequate for Persian (Microsoft
confirms this). Systems that use it for Persian usually use the hack that
Bob described.
roozbeh
On Fri, 12 Oct 2001 [EMAIL PROTECTED] wrote:
> It isn't. That is, Persian YEH isn't available in CP1256.
>
> I've seen some Far
On Thu, 11 Oct 2001, Mark Leisher wrote:
> Can someone tell me how the Persian YEH (U+06CC) is dealt with in a CP1256
> context? Has the official mapping changed from the following page?
>
> http://www.microsoft.com/globaldev/reference/sbcs/1256.htm
CP1256 has never supported FARSI YEH.
> Or
It isn't. That is, Persian YEH isn't available in CP1256.
I've seen some Farsi fonts and a common hack is to swap the isolate & final
forms of Arabic Yeh (d237, U+064A) with those of Alef Maksura (d236,
U+0649), thus turning d237 into a Farsi yeh, and permitting d236 to be used
should they need
At 18:31 10/11/2001, Vladimir Ivanov wrote:
>Third form is a combination of the fourth form (from right to left) and
>Kashida U+0640.
Er, no. The third form is the initial form in this particular typeface,
which happens to have rather a long connecting stroke. Trust me, I know
this typeface in
18 matches
Mail list logo
