Re: Information/Links for Myanmar Localization



On Wed, 2005-07-27 at 11:43 -0700, Ngwe Tun wrote:
 
> Now, I've placed some presentations which included how we did
> Localization in OSS Platform
> (http://www.openmm.org/downloads/presentations/) and Myanmar OpenType
> Font (Under GPL License, It's jointly developed by KhmerOS.info
> Experts) http://www.openmm.org/downloads/Fonts/OpenType/ It might be
> spacing fixed version of Myanmar OpenType Font and that's absolutely
> conformed UTN11. But It is under developing condtion. Let me know some
> bugs and change log.

Its great to see your work being made public and collaboration with
KhmerOS people :)

The font has copyright information saying all rights are reserved.
If/when you licence it under the GNU GPL, please read the following:

http://www.gnu.org/licenses/gpl.html#SEC4

And please add the font exception recommended by the FSF:

http://www.gnu.org/licenses/gpl-faq.html#FontException

> We have to submit revise letter to ISO IEC. So, we are helping to
> submit revise letter. I would like to get some comments and
> suggestions. I guess so it would be getting next year or depends on
> situation. 

I can proofread the revised letters for you, but I don't know any
Burmese so I will be of limited help.

> Yes, I did with Mr.Handa to support Burmese in M17N+Pango. Shoul you
> try in this URL (http://www.m17n.org/m17n-lib/demo/m17n-demo.html) We
> used TrueType font with PUA code points. That's pretty runs on Gnome
> Desktop. Please check up at
> (http://www.openmm.org/downloads/screenshots/ )

Very nice :) Are the source for the translations I see in those
screenshots available in the .iso?

> You can get some file to install Myanmar Enabling Kit.
> (http://www.openmm.org/downloads/isos/ )

Excellent. It would be nice if you could create a dir containing the
patches that need to be applied in order to change standard software
into stuff that supports Burmese, in order for maintainers of that
software to integrate your changes.

> I was a plan to submit glibc maintainers. Not yet. I would like to
> know about procedures in new locale submission. I really needed some
> contact information for locale submission. 

http://www.student.uit.no/~pere/linux/glibc/

When the locale is complete and finished, do the following:

Create an account in the bug tracking system:
http://sources.redhat.com/bugzilla/createaccount.cgi

Read some other locale bugs (especially the ones at the bottom):
<http://sources.redhat.com/bugzilla/buglist.cgi?product=glibc&component=localedata&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&&order=bugs.bug_severity,bugs.bug_severity%2Cbugs.bug_severity>

File a wishlist bug against the glibc localedata component:
http://sources.redhat.com/bugzilla/enter_bug.cgi?product=glibc&component=localedata&bug_severity=enhancement

Be sure to mention the proposed updates to the Burmese Unicode block if
the locale makes use of them.

You should also send the locale to the following locale groups:

belocs: http://belocs.alioth.debian.org/
file a bug here: http://alioth.debian.org/tracker/?atid=411660&group_id=30650&func=browse

cldr: http://www.unicode.org/cldr/
read this: http://www.unicode.org/cldr/filing_bug_reports.html
read bugs/file a bug here: http://dev.icu-project.org/cgi-bin/locale-bugs

> I've not tested in xfreex6 and xwindows servers.

No, I mean the xorg/xfree86 x servers contain a burmese keyboard layout.
Have you tried it?

> But I'm looking for IIIMF Keyboard layout and other better tools.

Google shows some free software written for that, perhaps you could
adapt it:

http://www.google.com/search?q=IIIMF

> I made the width problem internally in fonts. Don't fix it up. Should
> you use new opentype font. I got some information requesting helps
> from several mailing lists. I had known exactly what I did it in
> internally. And It's commercial fonts especially for Windows User. As
> far as I know, Windows was not supported for Burmese Unicode. So, I
> broke the rules of Unicode Standard and some modification in Myanmar
> Code Point (U+1000 to U+1900) area. It's not useless for my
> implementation and localization. I can figure out our encoding issues.
> I can dream future version of windows and OSS platforms. 

OK

> SIL Graphite Burmese stuff is good for temp using. I can't rely on
> this stuff because Native Rendering Engines (Pango, Qt, Uniscribe,
> ATT) are more reliable on each Platform. But I tried hard testing in
> Graphite stuff. 

OK

> Yes, I've downloaded this stuff. But there is a little issue in
> conversion text. Now All Links are dead.
> http://www.girlza.com/my.php
> http://www.girlza.com/my.php?display=source 

Yes, he hosts it on a dialup connection, so it is a bit slow and often
down.

> We have implemented TecKit Conversion program for transliteration
> purpose. Now, I organizing some ASCII Burmese font's layout to develop
> Conversion program with TecKit based. It's quiet easy and you should
> learn from www.thanlwinsoft.org

Thanks

> I don't have debian package. But you can run source packages by
> packages in our iso files. Let me know any difficulties and bugs.

OK. Please try to get your changes included into the official
distributions of these software

-- 
bye,
pabs

http://pabs.zip.to

Attachment: signature.asc
Description: This is a digitally signed message part



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]