headers
abysta | 17 Jun 2008 20:57
Picon
Favicon

new letters/glyphs

Hello!

1. The Unicode Technical Committee made a decision to encode two new letters: CYRILLIC CAPITAL LETTER PE
WITH DESCENDER (U+0524) and CYRILLIC SMALL LETTER PE WITH DESCENDER (U+0525). The code points won't be changed.

http://www.unicode.org/alloc/Pipeline.html

2. The UTC made a decision to change glyphs of U+04BE/F (the descender became straight) and U+04A8/9.

http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3435.pdf

Please, see this font http://narod.ru/disk/970866000/DejaVuSansAbk.ttf.html (it has new letters and glyphs).

Abkhaz user community would like DejaVu fonts to have these new letters and glyphs.

Regards :)

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
Permalink | Reply |
headers
Michael Everson | 18 Jun 2008 13:38
Favicon
Gravatar

Re: new letters/glyphs

Attached is a TTF with additions for Cyrillic. I have changed or 
added the following characters:

0484
0487
0514
0515
0516
0517
0518
0519
051E
051F
0524 (not formally encoded)
0525 (not formally encoded)
0526 (not formally encoded)
0527 (not formally encoded)
A640
A641
A642
A643
A648
A649
A64A
A64B
A64E
A64F
A652
A653
A656
(Continue reading)

Permalink | Reply |
headers
Michael Everson | 18 Jun 2008 11:06
Favicon
Gravatar

Re: new letters/glyphs

Hi everyone.

I wrote http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3435.pdf and have a 
few comments.

At 22:57 +0400 2008-06-17, abysta@... wrote:

>1. The Unicode Technical Committee made a decision to encode two new 
>letters: CYRILLIC CAPITAL LETTER PE WITH DESCENDER (U+0524) and 
>CYRILLIC SMALL LETTER PE WITH DESCENDER (U+0525). The code points 
>won't be changed.
>
>http://www.unicode.org/alloc/Pipeline.html

The characters have not yet been accepted by WG2 and won't get on a 
ballot until October. The promise is that they won't be changed. 
That's my promise. I can't imagine ANY reason why they would be 
changed. HOWEVER! (I must make this disclaimer...) A promise is not a 
guarantee. Realize that you are embarking on "early implementation" 
and "Caveat Implementor" applies.

>2. The UTC made a decision to change glyphs of U+04BE/F (the 
>descender became straight) and U+04A8/9.
>
>http://std.dkuug.dk/jtc1/sc2/wg2/docs/n3435.pdf

These glyph corrections have been added to FDAM5 and are quite safe to make.

>Please, see this font 
>http://narod.ru/disk/970866000/DejaVuSansAbk.ttf.html (it has new
(Continue reading)

Permalink | Reply |
headers
Ben Laenen | 18 Jun 2008 13:49
Picon

Re: new letters/glyphs

On Wednesday 18 June 2008, Michael Everson wrote:
> Has the DejaVu community's have a policy in early implementation?

We generally wait for adoption of new glyphs that were added to unicode 
until the new unicode release is made. Last time we jumped a bit 
earlier on the 5.1 ship, during beta I think -- we've been told 
somewhere that code points don't change anymore after that (I guess 
that can be seen as early implementation compared to other fonts :-) ) 
We're most wary about creating future compatibility problems by using 
code points that might change later on.

Until now we've put the glyphs that were scheduled to appear in a future 
version of unicode in the private use area, and moved them to their 
proper encoding points later. I guess we could follow the same method 
for Abkhaz?

Are there people with different ideas on the list?

Greetings
Ben

-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
Permalink | Reply |
headers
Michael Everson | 18 Jun 2008 22:46
Favicon
Gravatar

Re: new letters/glyphs

At 13:49 +0200 2008-06-18, Ben Laenen wrote:
>On Wednesday 18 June 2008, Michael Everson wrote:
>>  Has the DejaVu community's have a policy in early implementation?
>
>We generally wait for adoption of new glyphs that were added to 
>unicode until the new unicode release is made.

Please remember that the Unicode Standard and ISO/IEC 10646 are both 
equivalent, and either may be released before the other.

>Last time we jumped a bit earlier on the 5.1 ship, during beta I 
>think -- we've been told somewhere that code points don't change 
>anymore after that

Strictly speaking, when an FDAM is issued by ISO/IEC JTC1/SC2, no 
further technical changes can be made. So an early implementation for 
that

>(I guess that can be seen as early implementation compared to other 
>fonts :-) )  We're most wary about creating future compatibility 
>problems by using
>code points that might change later on.

Understandable.

>Until now we've put the glyphs that were scheduled to appear in a 
>future version of unicode in the private use area, and moved them to 
>their proper encoding points later. I guess we could follow the same 
>method for Abkhaz?
(Continue reading)

Permalink | Reply |

Gmane