Re: [nvda-translations] Progress of userguidelines and the newer version of it.
- From: Him Prasad Gautam <drishtibachak@xxxxxxxxx>
- To: nvda-translations@xxxxxxxxxxxxx
- Date: Thu, 15 Nov 2012 08:00:06 +0545
Hi,
Sorry for my hard felt statement. I understand the ground of adopting
the policy of using the stable version of inherted system. I am
neither negative nor frustated. It was just a statement of the
reasons for not doing the rest of translation hurrily. Since i did not
know that there is a such a change on the manual, I planned to
complete it before the next release. Let me clear that there exists no
Nepali TTS except developed by myself in Espeak system. I am
distributing the translated version of NVDA. for local users who are
in touch to me. Be clear that if I got a chance of a contact to any
local user, instead of saying them to download the test version of
Nepali TTS from web; i myself will provide it because it is developed
by me and sent to Jonathan. Why to show some where if the item is in
my pocket. My concern was with whom I may not reach by any means nor
they know that I had the system.
Regarding the update guideline, merge the newer onee. I will translate
the newer guideline for the rest chapter (9,10 and 11) and revised the
rest (1 to 8 and 12). I think that there will be no problem since I
can segregate it chapterwise.
On 11/15/12, Joseph Lee <joseph.lee22590@xxxxxxxxx> wrote:
> Hi,
> Just to give heads up on status of Korean translations and
> related work:
> As Mesar said, we don't know when we the translators will see a
> message from Jamie that the stable version of 2013.1 will be out.
> However, my best guess would be around February or March of 2013
> (based on past messages I read).
> As for work itself, I think you might want to ask your community
> to test your translations to see if people can understand it.
> Also, ask others to help you with TTS (preferably people who has
> experiences with it). Same goes with user guide: I'm sure there
> would be people who would be happy to test the user guide to see
> if there are any errors in there, such as typos.
> This was my plan when I coordinated Korean translations:
> * Set a schedule and priortize what is required. Also, try to
> have something as a base to work on before you do serious
> translations, like speech engine, user support and so on.
> * Commit frequently so that others may test it with you.
> Speaking of testing: ask some members of your community (those
> who are good at computers) to test the snapshots regularly.
> * Set some translation or feature milesteveros so others may be
> notified on how far you've done.
>
> For Korean, I did:
> * June 2012: Studied the translation system and subscribed to
> this list. Also, contacted some mailing lists in Korea to see if
> there was any prior effort on NVDA Korean translations (I found
> someone who already translated many messages in Korean).
> * July 2012: Formed a mailing list of Korean translators and
> asked volunteers for some work. At that time, I worked on
> interface messages (the po file) while another translator worked
> on the user guide. Once they were ready (not 100%, but around 80
> to 90% done), I asked Mesar to upload the translation to the SVN
> server for processing.
> * August 2012: I asked around on the Korean mailing list to see
> what features were required in Korean NVDA, namely eSpeak voice
> in Korean and Hanja (Chinese) character support. Tning contined
> using Main snapshots.
> * September 2012: Downloaded the NVDA source code and built it,
> as I received a word from Jonathan that a version of eSpeak with
> Korean voice was available (this Korean voice data was worked by
> a Chinese person, and I and others tweaked it). Also, while I
> was working on eSpeak Korean, others searched for a database of
> Chinese characters needed in Korean. By end of the month, we
> combined both efforts into a single testing version.
> * October 2012: By this time, we decided that, given the time
> frame, it would be wise to introduce support for Korean braille
> later, as it needed much testing and work. Thus, we finalized
> our tentative Korean work, producing a Korean-specific NVDA with
> eSpeak voice on it (built from source code).
> Thus, in Korean language, there are two versions circulating
> around: the international version, which is NVDA 2012.3 itself,
> and a Korean version named 2012.3K with eSpeak voice on it (dev
> version, that is), as we priortized the voice also (just like
> your case). Once a stable eSpeak comes out
> and with Korean voice done, the K version will be no more - to be
> integrated to international version.
> As for Korean braille, there was a Korean table provided by
> BRAILLETTY. Mesar sent me the converted table, then I copied the
> table to the place where LibLouis (the translator) was instabbled
> and modified the NVDA source code to show Korean braille (for
> testing purposes). I and other Korean users (through me) are
> sending regular updates via a ticket that was opened recently,
> covering support for braille; we're also updating the braille
> table via SVN.
> To end it, I'd like to quote this Korean proverb (as an
> encouragement): "a collection of dust makes a big mountain" - I
> think, in order for a project like this to succeed, I think
> continued testing and help from the Nepali community would be a
> very valuable asset for your work. Good luck, and whenever you
> need help, we're here to help anytime, anywhere.
> Hope this helps.
> Cheers,
> Joseph (Korean translator)
> ----- Original Message -----
> From: Him Prasad Gautam <drishtibachak@xxxxxxxxx
> To: mesar.hameed@xxxxxxxxx
> Date sent: Wed, 14 Nov 2012 20:18:42 +0545
> Subject: [nvda-translations] Progress of userguidelines and the
> newer version of it.
>
> Hi Mesar,
> The translation of user guide up to chapter 8 and chapter 12 is
> already completed. I am doing the rest of work very slowly.
> Slowly,
> because the newer NVDA 2012.3 with Nepali translation could not
> be
> useable for my locale users. Perhaps the next release of NVDA
> may be
> able to provide Whole of my work to my language community. Its
> my bad
> luck that I myself developed Nepali Espeak voice first, sent it
> to
> Jonathan, Translated NVDA, WxPythonTrunk and prepared the Louis
> braille tables. As your policy, you only include the stable
> version of
> inherted system. However non of them ( The Espeak, WXWidgits and
> Louis) release their stable version prior to 2012.3 nor you dare
> to
> stay for their newer release. Though I have the Nepali Espeak
> Voice
> with me and I am using and providing to that person who has
> contacted
> me. Unless Nepali Espeak Voice is packed with NVDA, my work is
> worthless since there exists no next Nepali TTS yet. I am sure I
> will
> complete the rest of translation before your next release.
> Please release newer user guidelines to diff file. I myself will
> rearrange the topics and prepare it as the newer one. Be
> confirm, the
> mistakes will be not repeated. Do your work. Go ahead. It will
> helpful
> to me if you can inform me about the tentative time of next
> release of
> NVDA...
>
> --
> Him Prasad Gautam
> Kathmandu, Nepal
>
>
>
--
Him Prasad Gautam
Kathmandu, Nepal
Other related posts:
