I agree to set the languages as incomplete. Giving a percentage would be a nice way to present to the user via. the new website (translations page, which I will handle for now).
If we remove langauge files, we must be 100% sure that we are documenting what we are removing. Here's a good format for this: langname date removed current maintainer percentage complete Harry, if you are able to talk with the translation team and get a good listing of the languages, I would greatly appreciate it. I want to have good documentation of every lang file and it's maintainers so that we can quickly contact them when new translation keys are ready to be translated. The same format as shown above can be used for all languages, so you could simply make a spreadsheet containing these 4 elements, and where the language still exists, do not include the date remove field. I think this should help us. Harry, what's your aMSN contact address, so that I may contact you? ~Lee On 11/16/05, Youness Alaoui <[EMAIL PROTECTED]> wrote: > I think it's a good idea, or we can also set some languages as > "Incomplete" or "only XX% translated" or something like that... I would > suggest that for lang files having between 30 and 70% of the keys > translated, less than 30% should be removed but still keep a listing of > them somewhere in the wiki so we won't forget which languages were there > and removed. > > Thanks for noticing. > KaKaroTo > > On Wed, 16 Nov 2005 18:20:37 -0500, Harry Vennik <[EMAIL PROTECTED]> > wrote: > > > Hi, > > > > There are some really outdated langfiles. I think we cannot keep > > pretending > > that those languages are available, because those files are simply > > missing > > too many keys to be of any use. Examples are Korean, Tamil, Greeklish and > > Esperanto. But there are some more. > > > > Although it is hard to tell what should be the maximum number of missing > > keys > > - or the maximum time since the last update - I think we should make a > > decision, and remove some of the files. If someone ever volunteers to > > start > > working on any of those languages, we can restore the file from the > > attic, > > and tell the new volunteer: 'Hi, on our dark 'n dirty attic we found some > > horribly outdated langfile in your language. You can use it as a starting > > point if you like.' > > > > What do you guys think? > > > > Regards, > > > > Harry > > > > > > ------------------------------------------------------- > > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > > Register for a JBoss Training Course. Free Certification Exam > > for All Training Attendees Through End of 2005. For more info visit: > > http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click > > _______________________________________________ > > Amsn-devel mailing list > > Amsn-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > > > -- > KaKaRoTo > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. Get Certified Today > Register for a JBoss Training Course. Free Certification Exam > for All Training Attendees Through End of 2005. For more info visit: > http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click > _______________________________________________ > Amsn-devel mailing list > Amsn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/amsn-devel > ------------------------------------------------------- This SF.Net email is sponsored by the JBoss Inc. Get Certified Today Register for a JBoss Training Course. Free Certification Exam for All Training Attendees Through End of 2005. For more info visit: http://ads.osdn.com/?ad_idv28&alloc_id845&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
