Bug 19881

Summary: Berber orthographies in Latin and Tifinagh
Product: fontconfig Reporter: Roozbeh Pournader <roozbeh>
Component: orthAssignee: Keith Packard <keithp>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: medium CC: freedesktop
Version: 2.6   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments: Tamazight (tmz) orthography in Latin
Berber for Algeria (ber-DZ) orthography
Berber for Morocco (ber-MA) orthography in Tifinagh

Description Roozbeh Pournader 2009-02-01 14:18:05 UTC
ISO 639 does not really handle Berber language(s) well enough, and out current language tagging is not at its best for such languages either, but I did the best I can.

The Berber language(s) are written in Latin, Tifinagh, and Arabic across various different countries in northern Africa, in some places semi-official, in some places forbidden. ISO 639-2 assigns codes to three languages in the family, and classifies the rest under "ber", for "Beber (Other)". The three privileged ones are Kabyle (kab), Tamashek (tmh), and Zenaga (zen). ISO 639-3 considers "ber" and "tmh" to be language collections, putting 20 languages under "ber", and four under "tmh". At the same time, Berber speakers are somehow trying to standardize Berber under one umbrella of a Standard Tamazight (no code in ISO 639).

Glibc has two Berber locales at the moment, ber_DZ for Algeria and ber_MA for Morocco. Algeria has standardized on Kabyle, writing in Latin, but Morocco has standardized on Tifinagh.

I'm mostly trying to solve the glibc issue and make Berber localizations possible, so I'm attaching three orth files: kab.orth for Kabyle, ber_DZ.orth as its alias, and ber_MA.orth.
Comment 1 Roozbeh Pournader 2009-02-01 14:18:37 UTC
Created attachment 22444 [details]
Tamazight (tmz) orthography in Latin
Comment 2 Roozbeh Pournader 2009-02-01 14:19:06 UTC
Created attachment 22445 [details]
Berber for Algeria (ber-DZ) orthography
Comment 3 Roozbeh Pournader 2009-02-01 14:19:34 UTC
Created attachment 22446 [details]
Berber for Morocco (ber-MA) orthography in Tifinagh
Comment 4 Behdad Esfahbod 2009-02-03 13:48:04 UTC
In my tree:

commit 26f13225a0c4e65acbe280a47f7d25400ebf9660
Author: Roozbeh Pournader <roozbeh@gmail.com>
Date:   Sun Feb 1 20:46:23 2009 -0800

    Add Berber orthographies in Latin and Tifinagh scripts (bug #19881)

Comment 5 Behdad Esfahbod 2009-06-24 12:35:54 UTC
I believe I've fixed this in 2.7.0.  Please reopen otherwise.
Comment 6 xalidus 2011-01-14 18:28:37 UTC
Comment on attachment 22444 [details]
Tamazight (tmz) orthography in Latin

>#
># fontconfig/fc-lang/tmz.orth
>#
># Copyright © 2009 Roozbeh Pournader
>#
># Permission to use, copy, modify, distribute, and sell this software and its
># documentation for any purpose is hereby granted without fee, provided that
># the above copyright notice appear in all copies and that both that
># copyright notice and this permission notice appear in supporting
># documentation, and that the name of the author(s) not be used in
># advertising or publicity pertaining to distribution of the software without
># specific, written prior permission.  The author(s) make(s) no
># representations about the suitability of this software for any purpose.  It
># is provided "as is" without express or implied warranty.
>#
># THE AUTHOR(S) DISCLAIM(S) ALL WARRANTIES WITH REGARD TO THIS SOFTWARE,
># INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS, IN NO
># EVENT SHALL THE AUTHOR(S) BE LIABLE FOR ANY SPECIAL, INDIRECT OR
># CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE,
># DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER
># TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
># PERFORMANCE OF THIS SOFTWARE.
>#
># Tamazight (tmz)
>#
># Sources:
># http://www.omniglot.com/writing/kabyle.php
># http://www.geonames.de/alphkl.html
># 
>0041-005A
>0061-007A
>010C-010D
>0190
>0194
>01E6-01E7
>025B
>0263
>1E0C-1E0D
>1E24-1E25
>1E62-1E63
>1E6C-1E6D
>1E92-1E93

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.