Re: AbWord L10n update
Chris Leonard <[email protected]>
| Newsgroups | gmane.editors.abiword.devel |
|---|---|
| Message-ID | <CAHdAatb0pcOiOCZ6ixyjxnGAhKRJtEP5Ys6asxCCMhY+y+7new@mail.gmail.com> |
On Fri, Aug 10, 2012 at 7:00 AM, Ibraahiima SAAR <[email protected]> wrote: > > Hi Chris > Thanks for the update. Windows_Installer_.nsh_strings.po in Fulah has been > completed long before but is not on the list. Or I did not understand? > Regards > Ibrahima Dear Ibrahima, Unfortunately, Fulah was, in fact, the first case where we discovered that we cannot use the AbiWord NSH until the language is complete upstream in Unicode NSIS. I have transferred the lang ff Windows_Installer_.nsh_strings.po strings that you completed into an AbiWord NSH format. Unfortunately, the upstream Unicode NSIS strings for Fulah have not been completed, so simply having the AbiWord NSH completed is not enough to get Windows installer L10n. I will be posting two new PO files that contain the strings needed to localize Unicode NSIS in the Fulah language project (hopefully soon, I am still creating them manually). Fortunately these are not very big files. When those are completed, we will submit them upstream and eventually we will be able to use the Abiword NSH file you've completed. The positive side of this is that completing the Unicode NSIS L10n will benefit other Fulah localization efforts (well, at least their Windows installers) in some important packages like all Mozilla products (FireFox, etc.). I'm sorry if worked out that way for Fulah. Working to achieve 100% localization in any FOSS software stack is often a journey upstream. In this case, we are not sending our localizers on that journey alone, we are bringing the strings to our local community and will assist with upstreaming them. cjl