Bug 116 - ka.orth and Georgian capital forms
Summary: ka.orth and Georgian capital forms
Status: RESOLVED FIXED
Alias: None
Product: fontconfig
Classification: Unclassified
Component: library (show other bugs)
Version: 2.2
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Keith Packard
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-09-23 12:26 UTC by Owen Taylor
Modified: 2003-09-22 20:28 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Patch fixing ka.orth (375 bytes, patch)
2003-09-23 12:27 UTC, Owen Taylor
Details | Splinter Review

Description Owen Taylor 2003-09-23 12:26:44 UTC
I believe that ka.orth (Georgian) should not include the
range from U+10A0 to U+10C5, 

Reasoning:

 - Section 7.5 of the Unicode standard says:

        Case Forms. The Georgian alphabet is fundamentally caseless and
        is used as such in most texts. The scholar Akaki Shanidze
        attempted to introduce a casing practice for Georgian in the
        1950s, but it failed to gain popularity. In this typographic
        departure, the Asomtavruli forms serve to represent uppercase
        letters, while the lowercase is Mkhedruli or Nuskhuri. [...] The
        Unicode encoding of Georgian follows the Latin analogy: The
        range U+10A0..U+10CF is used to encode the uppercase capital
        forms (Asomtavruli), and the basic alphabetic range
        U+10D0..U+10FF may be regarded as lowercase (Mkhedruli or
        Nuskhuri).  [...]

 - The font that Microsoft ships with Windows XP that covers 
   Georgian (SylfaenARM) includes only the lowercase forms, so
   currently does not get picked up by ka.orth.
Comment 1 Owen Taylor 2003-09-23 12:27:27 UTC
Created attachment 58 [details] [review]
Patch fixing ka.orth
Comment 2 Owen Taylor 2003-09-23 13:28:39 UTC
2003-09-23  Owen Taylor <otaylor@redhat.com>
 
        * fc-lang/ka.orth: Remove Georgian capitals, they
        aren't used for normal writing. (Bug #116)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.