[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: common terms po
- To: Documentation and Translation <doc at arabeyes dot org>
- Subject: Re: common terms po
- From: Arafat Medini <lumina at silverpen dot de>
- Date: Wed, 21 Apr 2004 22:24:54 +0200
What a wonderful english...
I am against waiting till the file is clean.
As we can open it with our editors why do we have to wait?
And we don't have to stop working on it only cz it's not clean. We'll
have to do both. Work on clean-up
ara
On ر, 2004-04-21 at 22:10 +0200, Arafat Medini wrote:
> I am against waiting till the file is clean.
> I can't open it with my editor, so why wait?!
> Do we have to clean this out? Yep we have, ASAP? YES ASAP!
> But not work only because some strings are not clean, no way: first work
> and parallel clean.
>
> yours
> Arafat
>
>
> On ر, 2004-04-21 at 12:49 -0700, Nadim Shaikli wrote:
> > --- Arafat Medini <lumina at silverpen dot de> wrote:
> > > Salam,
> > >
> > > So I'll be the one who will coordinate the whole thing related to the
> > > common terms po. The file itself is in the cvs repository, how will
> > > we work on it?
> >
> > Before you start working on it you need to do a couple of things.
> >
> > 1. The common_terms.po file, as you and others have noted, might
> > not contain proper encodings (use 'msgfmt') and that needs to
> > be corrected before all else - see item-2 below
> >
> > 2. The improper encodings are coming from the actual translation
> > projects out there (ie. from KDE, Gnome, OpenOffice, etc, etc).
> > All projects should (dare I say it, _MUST_) look through the
> > common_terms files to see if the badly encoded terms are coming
> > from their directories.
> >
> > Once all the projects report back that they are 100% clean, we can
> > regenerate the common_terms file (again) and then and only then can
> > work on the file commence.
> >
> > This was all stated multiple times before. Arafat, a great deal of the
> > badly encoded translations are coming from Gnome files and they must be
> > looked into and cleaned-up ASAP.
> >
> > > one simple idea would be:
> > >
> > > you get the word, translate it, and add in brackets your translation.
> > > Like this we will have all translations visible besides each other,
> > > separated, and at the end of every 50 words I can go through all and
> > > make a majoritarian democracy work ;) I'll be the legislative...
> >
> > I'm not a fan of the mailing-lists idea (too much overhead). Once
> > the encodings are corrected in the various projects and the common_terms
> > file is regenerated (and its clean - msgfmt is your friend) we can
> > do something akin to the following,
> >
> > msgid "Translate me string"
> > msgstr ""
> > "[Arafat] My_translation_here"
> > "[Youcef] NO_my_translation_here"
> > "[Ossama] You_kidding_this_is_better"
> >
> > I think the idea is clear - ie. add a new translation if you think the
> > one listed there is not sufficient and append you name in brackets so
> > that tracking is simplified. Once all participants (per QAC's mandate)
> > have gone through a section in the file, all words/terms with multiple
> > translations can be discussed and agreed-upon on IRC (or whatever form
> > QAC chooses to do this).
> >
> > > Work begins on the 28th of April every one 50 words and I say here
> > > EVERY one. You have normally one week, but we can give two weeks.
> > > If you are not finished you get spam from me to finish the words. So
> > > start at your own risk.
> >
> > I also recommend that each person working on this file add a
> >
> > # YOUR_NAME stopped here (date)
> >
> > comment/tag so that others know where a person is at instead of
> > creating a multitude of files with numbers in them. This tag would
> > them be simply moved to the new location if further work is done
> > later by hand.
> >
> > Hope those suggestions help.
> >
> > Salam.
> >
> > - Nadim
> >
> >
> >
> >
> >
> > __________________________________
> > Do you Yahoo!?
> > Yahoo! Photos: High-quality 4x6 digital prints for 25
> > http://photos.yahoo.com/ph/print_splash
> > _______________________________________________
> > Doc mailing list
> > Doc at arabeyes dot org
> > http://lists.arabeyes.org/mailman/listinfo/doc
> >
>
> _______________________________________________
> Doc mailing list
> Doc at arabeyes dot org
> http://lists.arabeyes.org/mailman/listinfo/doc
>