Thread: just a q about translation status on webpage
Hi, There must be something wrong with http://www.pgadmin.org/pgadmin3/translation.php script. Latvian is 100% translated and when I look at mo file from webpage it's also translated but it still shows in translation page that only 73% is translated. Lafriks
Hi, Didn't you say that you had left some of them fuzzy? I certainly saw a couple of untranslated strings in your file and figuredthat there was no literal translation so you had left them (is that what fuzzy means?) Regards, Dave. -----Original Message----- From: pgadmin-hackers-owner@postgresql.org on behalf of Lauris Buksis Sent: Mon 8/16/2004 9:31 AM To: pgadmin-hackers@postgresql.org Subject: [pgadmin-hackers] just a q about translation status on webpage Hi, There must be something wrong with http://www.pgadmin.org/pgadmin3/translation.php script. Latvian is 100% translated and when I look at mo file from webpage it's also translated but it still shows in translation page that only 73% is translated. Lafriks ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
No, I translated all strings, but some are fuzzy because some words in these strings can't be translated. For example "New Cast" I translated as "Jauns Cast" and left it as fuzzy because there is no way to translate word "cast" to latvian. These are fuzzy in my opinion. Lafriks Dave Page wrote: > Hi, > > Didn't you say that you had left some of them fuzzy? I certainly saw > a couple of untranslated strings in your file and figured that there > was no literal translation so you had left them (is that what fuzzy > means?) > > Regards, Dave. > > > -----Original Message----- From: pgadmin-hackers-owner@postgresql.org > on behalf of Lauris Buksis Sent: Mon 8/16/2004 9:31 AM To: > pgadmin-hackers@postgresql.org Subject: [pgadmin-hackers] just a q > about translation status on webpage > > Hi, > > There must be something wrong with http://www.pgadmin.org/pgadmin3/translation.php script. Latvian is > 100% translated and when I look at mo file from webpage it's also > translated but it still shows in translation page that only 73% is translated. > > Lafriks > > ---------------------------(end of > broadcast)--------------------------- TIP 9: the planner will ignore > your desire to choose an index scan if your joining column's > datatypes do not match > > > ---------------------------(end of > broadcast)--------------------------- TIP 1: subscribe and > unsubscribe commands go to majordomo@postgresql.org >
Lauris Bukšis wrote: > No, I translated all strings, but some are fuzzy because some words in > these strings can't be translated. For example "New Cast" I translated > as "Jauns Cast" and left it as fuzzy because there is no way to > translate word "cast" to latvian. These are fuzzy in my opinion. No, fuzzy means that poedit did a guess, and nobody reviewed it yet. If you decided that Cast is not to be translated (I'd agree), than the final translation is "Jauns Cast". Not fuzzy! In any case, after the translation is completed, there may be no more fuzzy strings. Regards, Andreas
Ok, than fuzzy can be removed but anyway webpage doesn't show right status of translation. fuzzy strings in latvian translation are only about 5% and that means that there should be about 95% not 73% as it is now! Lafriks Andreas Pflug wrote: > Lauris Bukšis wrote: > >> No, I translated all strings, but some are fuzzy because some words in >> these strings can't be translated. For example "New Cast" I translated >> as "Jauns Cast" and left it as fuzzy because there is no way to >> translate word "cast" to latvian. These are fuzzy in my opinion. > > > No, fuzzy means that poedit did a guess, and nobody reviewed it yet. > If you decided that Cast is not to be translated (I'd agree), than the > final translation is "Jauns Cast". Not fuzzy! > > In any case, after the translation is completed, there may be no more > fuzzy strings. > > Regards, > Andreas > > > >
> -----Original Message----- > From: pgadmin-hackers-owner@postgresql.org > [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of > Lauris Bukšis > Sent: 16 August 2004 12:48 > To: pgadmin-hackers@postgresql.org > Subject: Re: [pgadmin-hackers] just a q about translation > status on webpage > > No, I translated all strings, but some are fuzzy because some > words in these strings can't be translated. For example "New > Cast" I translated as "Jauns Cast" and left it as fuzzy > because there is no way to translate word "cast" to latvian. > These are fuzzy in my opinion. I'm still not convinced that the script is 100% right (it seems I have to update the cache every time I want to view it otherwiseI get odd figures - and developer.pgadmin.org is right up the swanny), however, according to the one on www.pgadmin.org,there are 50 fuzzy strings in there which is why it's not at 100% (there are no untranslated ones - thatwas me misreading the file; sorry :-) ). Regards, Dave.
Yes now it is showing correct ;) still I'm quite sure that it was showing 73% today morning :) Lafriks On Pirmdiena, 16. Augusts 2004 21:51, you wrote: > > -----Original Message----- > > From: pgadmin-hackers-owner@postgresql.org > > [mailto:pgadmin-hackers-owner@postgresql.org] On Behalf Of > > Lauris Bukšis > > Sent: 16 August 2004 12:48 > > To: pgadmin-hackers@postgresql.org > > Subject: Re: [pgadmin-hackers] just a q about translation > > status on webpage > > > > No, I translated all strings, but some are fuzzy because some > > words in these strings can't be translated. For example "New > > Cast" I translated as "Jauns Cast" and left it as fuzzy > > because there is no way to translate word "cast" to latvian. > > These are fuzzy in my opinion. > > I'm still not convinced that the script is 100% right (it seems I have to > update the cache every time I want to view it otherwise I get odd figures - > and developer.pgadmin.org is right up the swanny), however, according to > the one on www.pgadmin.org, there are 50 fuzzy strings in there which is > why it's not at 100% (there are no untranslated ones - that was me > misreading the file; sorry :-) ). > > Regards, Dave. > > ---------------------------(end of broadcast)--------------------------- > TIP 9: the planner will ignore your desire to choose an index scan if your > joining column's datatypes do not match