Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
Le Mardi 09 Décembre 2003 08:14, Howard Bagcat a écrit : > Attached are the .mo and .po tl_PH translation files. The said translation > is on its partial stage. Dear Howard, Thank you very much for your partial delivery. It was published to CVS. For information, does Tagalog happen to be close to English? I noticed some translations like "Save as..." remained in English. Cheers, Jean-Michel ---(end of broadcast)--- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
Re: [pgadmin-hackers] Lithuanian translation files
Le Mardi 09 Décembre 2003 08:32, linas jankauskas a écrit : > Please find attached two files for a lithuanian translation. > I hope to finish this until the end of week, but you must notice, that > not all SQL terms can be translated to lithuanian without losing of its > meaning. F.E. all of my colleagues knows, what "View" means, but nobody > recognizes this term, if it's translated. This is the same problem, > which I have observed in Latvian translation progress. Thank you very much for this partial delivery. It was published to CVS today. Translating SQL software is always a very special case. Because users need to be able to write the SQL queries themselves, it is recommanded to preserve words like "View", "Triggers", etc... unless the word in your language is quite close or widely accepted. For example, in French, I kept "Vue" for "View". On the converse, I kept the English word for "Trigger". About shortcuts: the recommanded way is to keep the same shortcut letters, otherwise drop them (unless you test them in the application, but you will never be sure not to break something somewhere). Regards... Jean-Michel ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
Jean-Michel POURE wrote: Le Mardi 09 Décembre 2003 08:14, Howard Bagcat a écrit : Attached are the .mo and .po tl_PH translation files. The said translation is on its partial stage. Dear Howard, Thank you very much for your partial delivery. It was published to CVS. For information, does Tagalog happen to be close to English? I noticed some translations like "Save as..." remained in English. Tagalog currently isn't supported correctly in wxWindows (tl_PH locale missing). Patch and new win32 snapshot will be supplied later this day. Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
There's a new tagalog.patch file for wxWindows, to support Tagalog (Philippines) correctly. This should go to our snapshot some time, and should be used by our binary snapshots. Regards, Andreas ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
Hello Howard, as usual the fix I posted to wx was not accepted as-is; instead a lenghty comment was issued whether tl_PH is "Tagalog (Philippines)" or only "Tagalog". As a consequence, the fix committed to wx cvs is not equivalent to our fix, which will require some minor work again as soon as we upgrade our wx snapshot. Now I wonder if there are other countries where Tagalog is spoken. Maybe some parts of Malaysia, or Indonesia? Second, is there a native Tagalog Windows version available? Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
[pgadmin-hackers] Building wxWindows on MacOS X
Howdy. I'm new here. Nice to meet y'all. I'm trying to make wxWindows on my MacOS 10.3 system (as a prereq for pgadmin), I get the following error: ./bk-deps g++ -c -o monodll_dc.o -Ilib/wx/include/mac-2.5 -I./include -I./src/png -I./src/jpeg -I./src/tiff -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fpascal-strings -I./src/mac/morefilex -I/Developer/Headers/FlatCarbon -D__WXMAC__ -I./include -I./src/tiff -I./src/jpeg -I./src/png-DwxUSE_BASE=1 -DWXMAKINGDLL -O2 -Wall -fno-common -dynamic -fPIC src/mac/dc.cpp src/mac/dc.cpp:1282: error: parse error before `<<' token src/mac/dc.cpp:1287: error: parse error before `short' make: *** [monodll_dc.o] Error 1 I'm using wxWindows-pgAdmin3-20030831.tar.gz. Unfortunately, I don't have enough C++ knowledge to troubleshoot this. Can anyone lend a hand? I'm looking forward to getting pgadmin working in OS X! Thanks! Leon ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 09 December 2003 12:45 > To: Dave Page > Cc: [EMAIL PROTECTED]; Howard Bagcat; [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial) > > There's a new tagalog.patch file for wxWindows, to support Tagalog > (Philippines) correctly. > This should go to our snapshot some time, and should be used > by our binary snapshots. Hi Andreas, Compiled and built for Linux, however when compiling on Windows I get: C:\wxWindows_2.5\src\common\intl.cpp(3288) : error C2065: 'LANG_TAGALOG' : undeclared identifier C:\wxWindows_2.5\src\common\intl.cpp(3289) : error C2065: 'SUBLANG_TAGALOG_PHILIPPINES' : undeclared identifier I don't have the output from patch any more, but I remember it patching 2 files cleanly. Any ideas? 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
Re: [pgadmin-hackers] Building wxWindows on MacOS X
Leon Out wrote: Howdy. I'm new here. Nice to meet y'all. I'm trying to make wxWindows on my MacOS 10.3 system (as a prereq for pgadmin), I get the following error: ./bk-deps g++ -c -o monodll_dc.o -Ilib/wx/include/mac-2.5 -I./include -I./src/png -I./src/jpeg -I./src/tiff -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fpascal-strings -I./src/mac/morefilex -I/Developer/Headers/FlatCarbon -D__WXMAC__ -I./include -I./src/tiff -I./src/jpeg -I./src/png-DwxUSE_BASE=1 -DWXMAKINGDLL -O2 -Wall -fno-common -dynamic -fPIC src/mac/dc.cpp src/mac/dc.cpp:1282: error: parse error before `<<' token src/mac/dc.cpp:1287: error: parse error before `short' make: *** [monodll_dc.o] Error 1 I'm using wxWindows-pgAdmin3-20030831.tar.gz. Unfortunately, I don't have enough C++ knowledge to troubleshoot this. Can anyone lend a hand? I'm looking forward to getting pgadmin working in OS X! This very much sounds like a leftover of a cvs conflict, marking the conflicting lines. To start, please use our latest snapshot; the one you're using is too outdated for current pgAdmin3. Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
Dave Page wrote: -Original Message- From: Andreas Pflug [mailto:[EMAIL PROTECTED] Sent: 09 December 2003 12:45 To: Dave Page Cc: [EMAIL PROTECTED]; Howard Bagcat; [EMAIL PROTECTED] Subject: Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial) There's a new tagalog.patch file for wxWindows, to support Tagalog (Philippines) correctly. This should go to our snapshot some time, and should be used by our binary snapshots. Hi Andreas, Compiled and built for Linux, however when compiling on Windows I get: C:\wxWindows_2.5\src\common\intl.cpp(3288) : error C2065: 'LANG_TAGALOG' : undeclared identifier C:\wxWindows_2.5\src\common\intl.cpp(3289) : error C2065: 'SUBLANG_TAGALOG_PHILIPPINES' : undeclared identifier I don't have the output from patch any more, but I remember it patching 2 files cleanly. You're too fast... I just uploaded a changed patch. The original wx patch includes #ifndef/#defines for these two macros, you may replace the values with zero. Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial)
> -Original Message- > From: Andreas Pflug [mailto:[EMAIL PROTECTED] > Sent: 09 December 2003 16:47 > To: Dave Page > Cc: [EMAIL PROTECTED] > Subject: Re: [pgadmin-hackers] pgAdmin3 tl_PH translation (Partial) > > You're too fast... Aww shucks.. > I just uploaded a changed patch. > The original wx patch includes #ifndef/#defines for these two > macros, you may replace the values with zero. OK, thanks. Regards, Dave. ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
[pgadmin-hackers] Feature Request
I know I've been quiet lately, but I was working with pgAdmin3 today, and I wanted to print out the schema from a table, but there is no print feature. Is it possible to implement one, and if so how hard would it be? After finding I couldn't print, I cut and paste the schema out of the schema "preview" pane, only to find that the text didn't use the windows line delimiter. It seems that the lines in the window are terminated with just a line feed character, instead of the CRLF used byWindows. Can we change this? (BTW, I am hitting a UNIX postgres server, could this have caused the behaviour?) BTW to see what I mean, cut and paste into Notepad, it doesn't hide LF's like Wordpad does. ahp ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
Re: [pgadmin-hackers] Building wxWindows on MacOS X
Thanks, Andreas. I got the snapshot recently mentioned here (wxWindows-pgAdmin3-20031010-8). wxWindows now builds nicely. However, I can't build contrib/src/stc. Here's what happens: --- BEGIN ERROR --- g++ -dynamiclib -single_module -o ../../../lib/libwx_mac_stc-2.5.1.0.0.dylib stcdll_PlatWX.o stcdll_ScintillaWX.o stcdll_stc.o stcdll_AutoComplete.o stcdll_CallTip.o stcdll_CellBuffer.o stcdll_ContractionState.o stcdll_Document.o stcdll_DocumentAccessor.o stcdll_Editor.o stcdll_ExternalLexer.o stcdll_Indicator.o stcdll_KeyMap.o stcdll_KeyWords.o stcdll_LexAVE.o stcdll_LexAda.o stcdll_LexAsm.o stcdll_LexBaan.o stcdll_LexBullant.o stcdll_LexCPP.o stcdll_LexCSS.o stcdll_LexConf.o stcdll_LexCrontab.o stcdll_LexEiffel.o stcdll_LexEScript.o stcdll_LexFortran.o stcdll_LexHTML.o stcdll_LexLisp.o stcdll_LexLout.o stcdll_LexLua.o stcdll_LexMMIXAL.o stcdll_LexMatlab.o stcdll_LexNsis.o stcdll_LexOthers.o stcdll_LexPOV.o stcdll_LexPS.o stcdll_LexPascal.o stcdll_LexPerl.o stcdll_LexPython.o stcdll_LexRuby.o stcdll_LexSQL.o stcdll_LexScriptol.o stcdll_LexVB.o stcdll_LineMarker.o stcdll_PropSet.o stcdll_RESearch.o stcdll_ScintillaBase.o stcdll_Style.o stcdll_StyleContext.o stcdll_UniConversion.o stcdll_ViewStyle.o stcdll_WindowAccessor.o stcdll_XPM.o -framework Carbon -framework System-L../../../lib -install_name /usr/local/lib/libwx_mac_stc-2.5.1.dylib -compatibility_version 2.5.1 -current_version 2.5.1 -lwxtiff -lwxjpeg -lwxpng-lwxexpat -framework Carbon -framework System -lz -lpthread -liconv -lwx_mac_core-2.5 -lwx_base_carbon-2.5 /usr/bin/libtool: can't locate file for: -lwxtiff /usr/bin/libtool: file: -lwxtiff is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxjpeg /usr/bin/libtool: file: -lwxjpeg is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxpng /usr/bin/libtool: file: -lwxpng is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxexpat /usr/bin/libtool: file: -lwxexpat is not an object file (not allowed in a library) make: *** [../../../lib/libwx_mac_stc-2.5.1.0.0.dylib] Error 1 --- END ERROR --- I'm following the unix compilation instructions, but I did build wxWindows without GTK support. I'm assuming it's not required on the Mac. Is there a more OS X-centric install document anywhere? Thanks for your help! Leon On Dec 9, 2003, at 11:34 AM, Andreas Pflug wrote: Leon Out wrote: Howdy. I'm new here. Nice to meet y'all. I'm trying to make wxWindows on my MacOS 10.3 system (as a prereq for pgadmin), I get the following error: ./bk-deps g++ -c -o monodll_dc.o -Ilib/wx/include/mac-2.5 -I./include -I./src/png -I./src/jpeg -I./src/tiff -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -fpascal-strings -I./src/mac/morefilex -I/Developer/Headers/FlatCarbon -D__WXMAC__ -I./include -I./src/tiff -I./src/jpeg -I./src/png-DwxUSE_BASE=1 -DWXMAKINGDLL -O2 -Wall -fno-common -dynamic -fPIC src/mac/dc.cpp src/mac/dc.cpp:1282: error: parse error before `<<' token src/mac/dc.cpp:1287: error: parse error before `short' make: *** [monodll_dc.o] Error 1 I'm using wxWindows-pgAdmin3-20030831.tar.gz. Unfortunately, I don't have enough C++ knowledge to troubleshoot this. Can anyone lend a hand? I'm looking forward to getting pgadmin working in OS X! This very much sounds like a leftover of a cvs conflict, marking the conflicting lines. To start, please use our latest snapshot; the one you're using is too outdated for current pgAdmin3. Regards, Andreas ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED]) ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [pgadmin-hackers] Building wxWindows on MacOS X
Leon Out wrote: Thanks, Andreas. I got the snapshot recently mentioned here (wxWindows-pgAdmin3-20031010-8). wxWindows now builds nicely. However, I can't build contrib/src/stc. Here's what happens: --- BEGIN ERROR --- g++ -dynamiclib -single_module -o ../../../lib/libwx_mac_stc-2.5.1.0.0.dylib stcdll_PlatWX.o stcdll_ScintillaWX.o stcdll_stc.o stcdll_AutoComplete.o stcdll_CallTip.o stcdll_CellBuffer.o stcdll_ContractionState.o stcdll_Document.o stcdll_DocumentAccessor.o stcdll_Editor.o stcdll_ExternalLexer.o stcdll_Indicator.o stcdll_KeyMap.o stcdll_KeyWords.o stcdll_LexAVE.o stcdll_LexAda.o stcdll_LexAsm.o stcdll_LexBaan.o stcdll_LexBullant.o stcdll_LexCPP.o stcdll_LexCSS.o stcdll_LexConf.o stcdll_LexCrontab.o stcdll_LexEiffel.o stcdll_LexEScript.o stcdll_LexFortran.o stcdll_LexHTML.o stcdll_LexLisp.o stcdll_LexLout.o stcdll_LexLua.o stcdll_LexMMIXAL.o stcdll_LexMatlab.o stcdll_LexNsis.o stcdll_LexOthers.o stcdll_LexPOV.o stcdll_LexPS.o stcdll_LexPascal.o stcdll_LexPerl.o stcdll_LexPython.o stcdll_LexRuby.o stcdll_LexSQL.o stcdll_LexScriptol.o stcdll_LexVB.o stcdll_LineMarker.o stcdll_PropSet.o stcdll_RESearch.o stcdll_ScintillaBase.o stcdll_Style.o stcdll_StyleContext.o stcdll_UniConversion.o stcdll_ViewStyle.o stcdll_WindowAccessor.o stcdll_XPM.o -framework Carbon -framework System-L../../../lib -install_name /usr/local/lib/libwx_mac_stc-2.5.1.dylib -compatibility_version 2.5.1 -current_version 2.5.1 -lwxtiff -lwxjpeg -lwxpng-lwxexpat -framework Carbon -framework System -lz -lpthread -liconv -lwx_mac_core-2.5 -lwx_base_carbon-2.5 /usr/bin/libtool: can't locate file for: -lwxtiff /usr/bin/libtool: file: -lwxtiff is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxjpeg /usr/bin/libtool: file: -lwxjpeg is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxpng /usr/bin/libtool: file: -lwxpng is not an object file (not allowed in a library) /usr/bin/libtool: can't locate file for: -lwxexpat /usr/bin/libtool: file: -lwxexpat is not an object file (not allowed in a library) make: *** [../../../lib/libwx_mac_stc-2.5.1.0.0.dylib] Error 1 --- END ERROR --- Hi Leon, I'm the wrong person to ask about MacOS, so I post it on pgadmin-hackers. Actually, I'm not sure if that wx version compiles successfully at all on MacOS X. Still, some suspect: Maybe you need some "enable-monolithic" option to build correctly, wouldn't be the first platform that needs it. In case you don't get it compiled in any way, and nobody of the Mac guys can help you, please use a current wx cvs snapshot and try if that compiles for you. If it does, I can help you further to add needed patches, and we'll be upgrading our snapshot to get pgadmin3 MacOSX10.3 compatible. Regards, Andreas ---(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
Re: [pgadmin-hackers] Feature Request
Adam H. Pendleton wrote: I know I've been quiet lately, but I was working with pgAdmin3 today, and I wanted to print out the schema from a table, but there is no print feature. Is it possible to implement one, and if so how hard would it be? After finding I couldn't print, I cut and paste the schema out of the schema "preview" pane, only to find that the text didn't use the windows line delimiter. It seems that the lines in the window are terminated with just a line feed character, instead of the CRLF used byWindows. Can we change this? (BTW, I am hitting a UNIX postgres server, could this have caused the behaviour?) BTW to see what I mean, cut and paste into Notepad, it doesn't hide LF's like Wordpad does. If Wordpad shows the LF char, it is LFCR instead of CRLF. However, I'll have a look into this (win32 specific) thing. It's probably the STC control which misbehaves here. I haven't looked into printing so far; this is more than just a few lines of code. Printing needs drawing on the DC, font calculation, word wrap, pages, So a question to you around there: How important is printing to you? Regards, Andreas ---(end of broadcast)--- TIP 8: explain analyze is your friend
