Re: Fw: [HACKERS] Translators wanted
Serguei Mokhov [EMAIL PROTECTED] writes: Hello Peter, There was a little typo in line 73 in the original file libpq.pot: #: fe-connect.c:713 #, c-format msgid could not socket to non-blocking mode: %s\n missing the word 'set' between 'not' 'socket'... Yes. Peter noticed and fixed that typo in the fe-connect.c original a few weeks ago --- but it looks like he forgot to update de.po to match. I've committed the change to CVS. Thanks! regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Fw: [HACKERS] Translators wanted
The same applies as to my previous post... Sorry again. S. - Original Message - From: Serguei Mokhov [EMAIL PROTECTED] To: Peter Eisentraut [EMAIL PROTECTED] Sent: Wednesday, August 01, 2001 1:50 AM Subject: Re: [HACKERS] Translators wanted - Original Message - From: Peter Eisentraut [EMAIL PROTECTED] To: Serguei Mokhov [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Monday, July 16, 2001 4:03 PM Serguei Mokhov writes: Are there people working on the translation into the Russian language? If yes, then what messages are you working on and what encoding are you using? I can start translating the messages, just want to make sure so that we don't duplicate the effort. Use the koi8-r encoding unless you have strong reasons against it. Well, the KOI8-R is the standard encoding, no objection. However, Win32 apps use Windows-1251, which is pretty common on Win machines (e.g. pgAdmin tool on Windows will have to have messages in this exactly encoding), or console Windows apps by historical reasons (from DOS) use the 866 code page. If people write standard Windows or console client, which rely on the messages will get garbage most likely or will switch back to English ones. I can send the translated messages in the all mentioned encodings, but the problem is how will you place those files in the tree (according to the naming conventions ll[_RR].po one can have only one language per region per component) and plus, backbends probably have no way to know what kind of clients are connected to them and which encoding is more appropriate for the given client in the same language... These problems prevent different clients with the same language but different encoding schemes equally well display those messages to the user unless someone is willing (and has ideas how) to find a solution to the problems. Serguei ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Fw: [HACKERS] Translators wanted
Sorry for posting this messages into the list. It was intended for Peter E., but it looks like his personal mailbox is over quota... Hopefully, he will scan through the posts in the list once he's back from vacation, and the message won't get lost. Serguei - Original Message - From: Serguei Mokhov [EMAIL PROTECTED] To: Peter Eisentraut [EMAIL PROTECTED] Sent: Wednesday, August 01, 2001 1:38 AM Subject: Re: [HACKERS] Translators wanted Hello Peter, There was a little typo in line 73 in the original file libpq.pot: #: fe-connect.c:713 #, c-format msgid could not socket to non-blocking mode: %s\n missing the word 'set' between 'not' 'socket'... Despite I'm not a native English speaker/writer, I strongly believe it should be there: msgid could not set socket to non-blocking mode: %s\n I corrected the message in my translations; however, I didn't update the sources. The .PO file is sent to the pgsql-patches list. By the time you're back from vacation, I might have some other things translated... Have a good day, Serguei - Original Message - From: Peter Eisentraut [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Sunday, July 15, 2001 6:13 PM Subject: [HACKERS] Translators wanted Those of you who wanted to help translating the messages of PostgreSQL programs and libraries, you can get started now. I've put up a page explaining things a bit, with links to pages that explain things a bit more, at http://www.ca.postgresql.org/~petere/nls.html Please arrange yourselves with other volunteering speakers of your language. Results should be sent to the pgsql-patches list. You have a few days to ask me questions about this, then I'll be off on vacation and looking forward to a lot of progress when I get back. ;-) ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
