Le Jeudi 4 Septembre 2003 10:06, Dave Page a écrit :
> Hi Milan,
>
> You should be able to find all the details you require at
> http://www.pgadmin.org/pgadmin3/translation.php - if not please feel
> free to email the list with any questions.
>
> Which locale will you be translating:
> sh_SP Serbia
Dave Page wrote:
Which locale will you be translating:
sh_SP Serbian Latin Yugoslavia ISO8859-2
or
sr_SP Serbian Cyrillic Yugoslavia ISO8859-5
Actually, the canonical locale name is sr_YU, whichever charset is used.
At the moment, we don't have the option to implement a translation in
two
> -Original Message-
> From: Milan Kliska [mailto:[EMAIL PROTECTED]
> Sent: 04 September 2003 04:37
> To: [EMAIL PROTECTED]
> Subject: [pgadmin-hackers] pgAdmin3 translation
>
>
> Hey,
>
> I'm interested in translating pgAdmin to Serbian. Please
Hey,
I'm interested in translating pgAdmin to Serbian. Please let me know how
to proceed.
Cheers,
Milan Kliska
---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
On Monday 30 June 2003 23:13, you wrote:
> I would say "no" currently due to my busy summer, but thinking on it more,
> I'll probably have the oppurtunity to translate pgAdmin3 until the end of
> July. I'll write an article about i18n in a Hungarian Linux Gazette soon
> and I'll show the method of
On Monday 30 June 2003 16:13, Serguei Mokhov wrote:
> Your proposal sounds like fun. I can also derive fr_CA
> version of it if needed ;)
>
> Thank you for considering me doing pgAdmin3 Russian
> translation.
Welcome Russia! Thank you very much for contributing your time and work. Do
not hesitate
Hello Jean-Michel,
Your proposal sounds like fun. I can also derive fr_CA
version of it if needed ;)
Thank you for considering me doing pgAdmin3 Russian
translation.
-s
- Original Message -
From: "Jean-Michel POURE" <[EMAIL PROTECTED]>
To: "Serguei A. Mokhov" <[EMAIL PROTECTED]>
Sent: J
On Mon, 30 Jun 2003, Jean-Michel POURE wrote:
> Can I add you as a Swedish translator. No need to translate now. You can wait
> until you find time to do so.
Sure, do that.
--
/Dennis
---(end of broadcast)---
TIP 9: the planner will ignore your
Dear Dennis,
> I've translated a lot of things before (all using emacs). That is not a
> problem. I also saw what you/someone wrote in the guidelines about upper
> case strings. But still, it's not good.
>
> Now I'm tempted to look at the source instead and understand why it has to
> be like this.
On Tuesday 24 June 2003 16:46, Darko Prenosil wrote:
> Confirmed ! I hope this weekend should be enough time to do it.
> I do not know how many users here in Croatia use the pgAdmin, but however,
> I translated PostgreSQL server messages , why not pgAdmin's ?
>
> I guess PostgreSQL service manager
Thanks Hiroshi, that's great news. Translation commited.
Regards, Dave.
> -Original Message-
> From: Hiroshi Saito [mailto:[EMAIL PROTECTED]
> Sent: 23 June 2003 06:43
> To: [EMAIL PROTECTED]; Andreas Pflug; Dave Page
> Cc: [EMAIL PROTECTED]
> Subject: Re: [pg
Hi Jean-Michel.
Though it became very late, Japanese-po[ja_JP] file is sent.
But, it doesn't think that it is an end completely in this.
It wants to cope with the expansion of pgadmin3 and addition.
Encoding was written with UTF-8 unlike the first thought.
regards,
Hiroshi-Saito
> Hi Jean-Michel
Hi Jean-Michel.
> From: "Jean-Michel POURE" <[EMAIL PROTECTED]>
(snip)
> > By the way, save a lot of time using poedit from
> > poedit.sourceforce.net.
>
> A happening from tonight...
>
> With kindest regards,
> Hiroshi-Saito
It is still in the middle of the work.
http://cre-ent.skcapi.co.jp/~
Hi Jean-Michel.
From: "Jean-Michel POURE" <[EMAIL PROTECTED]>
> On Thursday 19 June 2003 01:24, Hiroshi Saito wrote:
> > I will being written it with the code for EUC_JP.
> > It thinks that it will be made by FreeBSD.
> > An environment hasn't been able to be made yet though it is trying to
move
>
On Thursday 19 June 2003 01:24, Hiroshi Saito wrote:
> I will being written it with the code for EUC_JP.
> It thinks that it will be made by FreeBSD.
> An environment hasn't been able to be made yet though it is trying to move
> it for the confirmation.
Independently of your choice, we can always
Hi Andreas.
> Hi Hiroshi,
>
> do you think you could contribute the Japan translation for pgadmin3?
It is a preparation grade now.
Believes that this succeeds securely from the conditions here.
> You would have to copy pgadmin3.pot to ui/ja_JP/pgadmin3.po, edit it
> with poEdit (poedit.sourcefor
Hi Hiroshi,
do you think you could contribute the Japan translation for pgadmin3?
You would have to copy pgadmin3.pot to ui/ja_JP/pgadmin3.po, edit it
with poEdit (poedit.sourceforge.net) and update from time to time using
the "Catalog/update from POT file" function if strings have been added.
Dear fellow developers,
I prepared pgAdmin3 for translation:
To enable translation of pgAdmin3 strings, all candidates need to be marked.
1) A string that will not be translated (queries, log entries, setting
tags etc)
will be declared with wxT(""), as
Le Vendredi 30 Mai 2003 10:15, Andreas Pflug a écrit :
> I'm lacking any experiences with that, but why not?
I wonder why ./configure options include --enable-unicode --enable-gtk2,
that's all. A look at poEdit might clarify some issues (why does it use
wxWindows2.5 cvs?).
Thanks for other expl
Jean-Michel POURE wrote:
As usual, I have several silly questions:
1) wxGTK versions
Could you outline the Unicode differences between:
- wxGTK2.4 linked against GTK1.2,
- wxGTK2.4 linked against GTK2.0+unicode support,
- wxGTK2.5cvs linked against GTK2.0+unicode support (poEdit uses only this
v
Le Jeudi 29 Mai 2003 23:46, Andreas Pflug a écrit :
> Jean-Michel, could you give us hints on how to implement the xgettext
> process, unix and w32? The __() macro is intended to be the short form
> for gettext_noop().
Thanks Andreas. This is thrilling and so exciting.
Before tagging source files
Sorry screwed up my mail accounts, reposting:
Dear fellow developers,
I prepared pgAdmin3 for translation:
To enable translation of pgAdmin3 strings, all candidates need to be
marked.
1) A string that will not be translated (queries, log entries, settin
22 matches
Mail list logo
