Wunna Ko Ko wrote
Dear Javier SOLA,
On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote:
Wunna Ko Ko
Wunna Ko Ko wrote
Dear Javier SOLA,
Thanks for your information.
I understand the situation.
The latest proposal change has already been accepted by UTC, and at
stage 6 by ISO/IEC.
Please check
http://www.unicode.org/alloc/Pipeline.html
Great
Our team would like to start with Internationalization, like line
breaking, searching, collation, etc. So, translation process is not
necessary at this stage, I think. It is the only possible step right
now, as far as I understand.
It is. You can start working on the OpenOffice locale file, as well as
the collation sequence, if you have the correct ordering sequence.
OK. I & my team will start working on Locale files.
You can also start patching the OpenOffice files that are required to
include Burmese among the existing locales.
Searching should not be a problem.
It has still problem. It can't get exact search till now.
We also have some problems for Khmer in OpenOffice. I have to figure out
what it really is. We can search for full syllables, but not for parts
of it, even if it is a correct sequence.
Line-breaking is handled by the ICU library, which is used by
OpenOffice. You have to look onto how Thai is handled, and do something
similar, the simpler way is to do it dictionary/based... but you need a
word-list.
Our idea is starting the line-break by syllable break. We will place
the syllable segmentation rules. Where should we put?
The breakiterator of the ICU library, but I do not have a clue of how it
is done. Can Myanmar be broken at the end of any syllable? You do not
need to wait for the end of a word?
A spell-checker is also a very useful feature to work on. As Microsoft
will not localize to Myanmar yet for a number of years, a spell checker
would give you a very strong reason for people to change to OpenOffice.
Javier
With Best Regards,
Please look into
http://www.khmeros.info/tools
to see which files already have Burmese included, and which do not. If
you can prepare patches for the other files, wonderful, otherwise we
will help you. The most important thing is to gather all the necessary
information for the locale file and collation.
Javier
Could you please let me know how can I create a project to do I18n?
With Best Regards,
Wunna Ko Ko
On 8/11/07, Javier SOLA <[EMAIL PROTECTED]> wrote:
Dear Wunna Ko Ko,
Very good to hear from you.
The first step for localisation of Burmese is to have support for your
script and fonts.
Support for Myanmar in Linux is still not available. Is tarted some work
on it with Ngwe Tun, but we did not continue because the state of
Unicode Burmese was unclear, I am not sure what the state of the latest
proposal for change is now.
Burmese is not officially supported by Microsoft Windows, but there are
ways around it. This support should already be enough to start the
localization and translation process.
Does NLP already have a glossary of words for computer use in Myanamar?
We can give you a first list of about 1,500 words that you should have
in order to start the translation work in a coherent way (all
translators translating the same word in the same way).
Please look at:
http://l10n.openoffice.org/
http://www.khmeros.info/tools
for information about OOo localization.
Regards,
Javier
Wunna Ko Ko wrote
Dear All,
I am the team leader of the Myanmar NLP research center, organized and
funded by Myanmar Government.
Is there anybody who is working on Burmese Language for OO projects?
We would like to start with I18n by creating locale and go to the
localization by translating OO.
I would like to know whether there is anybody working on it and how
much level has been developed.
With Best Regards,
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
