Re: [nvda-translations] About the internationalization of the official website.
- From: Mesar Hameed <mesar.hameed@xxxxxxxxx>
- To: nvda-translations@xxxxxxxxxxxxx
- Date: Sun, 9 Sep 2012 20:18:10 +0100
Hi,
Yes, I have just enabled zh_CN, its just a config file that needs to be
modified, to include the language code and the name of the language, and the
scripts build all po files.
by the way, if the language names are wrong thats easely fixed, but i
just googled for example:
arabic in arabic, and copied the name from wikipedia.
german in german, japanese in japanese, korean in korean, etc.
So if any of the language names before the percent is wrong please email
me privately with the correct name.
Thanks,
Mesar
On Sun 09/09/12,12:03, Joseph Lee wrote:
> Hi,
> Ah, that'll be because ZH po files are not there.
> Cheers,
> Joseph
>
> -----Original Message-----
> From: nvda-translations-bounce@xxxxxxxxxxxxx
> [mailto:nvda-translations-bounce@xxxxxxxxxxxxx] On Behalf Of Aaron
> Sent: Sunday, September 09, 2012 9:09 AM
> To: nvda-translations@xxxxxxxxxxxxx
> Subject: Re: [nvda-translations] About the internationalization of the
> official website.
>
> Dear Mesar,
>
> The demo site looks good, just wondering if Chinese index page will be
> provided and options will be shown on the navigation bar?
>
> thanks,
> Aaron
>
> Sent from iPhone
>
> On 2012/9/9, at 23:15, Mesar Hameed <mesar.hameed@xxxxxxxxx> wrote:
>
> > Hi team,
> >
> > Those of you who have had the time to try the demo, is there anything
> > very bad that should stop us from using this system, or should be
> > investigated further?
> >
> > I think i have invited everyone, but the team page seems to be quite
> > wrong, only shows a few names.
> >
> > Thanks,
> > Mesar
> > On Fri 31/08/12,17:56, Mesar Hameed wrote:
> >> Sorry forgot to say, the system doesnt have any email notifications at
> the moment, so just svn update yourself.
> >>
> >>
> >> On Fri 31/08/12,17:55, Mesar Hameed wrote:
> >>> Hi all, Juan,
> >>>
> >>> Your suggestion is good, especially since we want to do the community
> add-on pages.
> >>>
> >>>
> >>> Jamie, Mick and I discussed this generally in the past and we have
> >>> some conserns which remained unresolved at the time.
> >>>
> >>> 1. Incase people become busy, or the language team dies, what should
> >>> be done for that language?
> >>> The idea is to have good and uptodate information, but if no one is
> >>> dooing a good job for the language what should be done in that case?
> >>>
> >>> One solution would be to use po files, and if the translation is not
> >>> updated, the default english messages would be displayed.
> >>> This is what I have now implemented.
> >>>
> >>> 2. what belongs on this multilingual website, and what doesnt?
> >>> Maybe the people who run existing language websites will feel we are
> >>> taking content that belongs there?
> >>> But looking at the community page on nvda-project, not that many
> languages have websites.
> >>>
> >>> 3. people generally dont enjoy editing wiki pages online.
> >>>
> >>> = potential solution =
> >>> a website that uses svn for its data and translations, since
> >>> everyone is happy with text editors or poedit.
> >>>
> >>> I have made a demo site here:
> >>> http://testing.mesarhameed.info
> >>>
> >>> The website is controlled from svn, you can svn checkout:
> >>> https://subversion.assembla.com/svn/nvdacommunitywebsite
> >>> You can start committing as soon as you accept the assembla invitation
> to this svn repository.
> >>>
> >>> == how does it work ==
> >>> pages are written in english, using markdown, the filename extension
> >>> is .mdwn It is also easy to learn, just a few differences between
> >>> markdown and text2tags (t2t)
> >>>
> >>> When anyone commits a new or changed mwn file, the system updates or
> >>> creates po files for that page.
> >>> then we svn update, to get the new po, and we can open it in poedit to
> translate it as usual.
> >>>
> >>> = disadvantages =
> >>> All information that has to be localized should exist in the mwn
> >>> file, For example it is quite ugly to add a new section in Swedish which
> doesn't exist in english.
> >>> It shouldn't be a real problem.
> >>>
> >>> if someone wants to edit the website using the web interface, they
> >>> edit the english mdwn, not the localizations.
> >>> For example if i read the french download page, and i press edit, i
> >>> expect to edit french content, but actually i edit english mdwn file.
> >>> So for the time being editing from the web is disabled.
> >>>
> >>> rtl problems: probably doesnt look right, text displayed on the left
> >>> instead of on the right, need to ask for sighted help to check.
> >>>
> >>> = what to do next =
> >>> Please test the system, and if you think it is usable we can change
> >>> the url to something more suitable.
> >>>
> >>> Feel free to edit or add any new mdwn files or po files.
> >>>
> >>> Discuss
> >>>
> >>> Thanks,
> >>> Mesar
> >>> On Wed 29/08/12,11:01, quetzatl wrote:
> >>>> Hi all, specialy Jamie and Mesar.
> >>>>
> >>>> Lately I come to reflect on the importance of a possible
> >>>> translation of the official website of NVDA to each of the
> >>>> languages into which translates the program.
> >>>>
> >>>> This does not mean the loss of all the effort that is already in
> >>>> the NVDA community, but would be offer an official website in
> >>>> several languages assuring that users of the web content really are
> >>>> reading official project, rather than informal content of the
> >>>> responsibility of each community websites in each of the languages.
> >>>>
> >>>> I know this would be a great job for translators, at least
> >>>> initially, and I don'tknow if it is technically possible to do so
> >>>> in the NVDA site as it is currently organized, although many other
> >>>> projects such as ReactOS, libreoffice, etc., Do have this type of
> >>>> system I propose.
> >>>>
> >>>> What do you think about this? Could we do this for NVDA?
> >>>>
> >>>> Particularly for me, although I suppose a lot more work, would be
> >>>> willing to translate the NVDA website.
> >>>>
> >>>> Regards.
> >>>>
> >>>> Juan.
> >>>>
> >
>
>
Other related posts:
