Re: [Gimp-developer] Re: [Gimp-docs] Wording in German: Toolbox
On Mon, 2004-07-26 at 17:56, Nathan Carl Summers wrote:
> >
> > So, what do you guys think: "Werkzeugfenster" or "Werkzeugkasten"?
>
> I don't speak German, but Werkzeugfenster sounds cooler than
> Werkzeugkasten. In fact, I wouldn't mind a "Werkzeugfenster" T-shirt.
Dare I suggest Werkzeugkastenfenster? ("Toolbox window")
--
Jeff
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Re: [Gimp-docs] Wording in German: Toolbox
Roman Joost <[EMAIL PROTECTED]> writes: > This mail is for "translating" the Toolbox into German. I wasn't sure > how to translate the Toolbox to German for the manual. But please, hold > your breath and let me explain why. > > So, what do you guys think: "Werkzeugfenster" or "Werkzeugkasten"? I don't speak German, but Werkzeugfenster sounds cooler than Werkzeugkasten. In fact, I wouldn't mind a "Werkzeugfenster" T-shirt. Rockwalrus ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 16 bit Gimp?
It would be nice to be prove wrong, but I am not aware of such a plugin. Dave's (dcraw author) own "plugin" is just a simple "text like" interface o dcraw. My work is based on PTJ rawphoto, but it is already much better, I believe. Have a look at http://pages.quicksilver.net.nz/pepe/d70/Nikon_D70_on_Linux.html if you like. -Joseph David Neary wrote: Hi, Sven Neumann wrote: Joseph Heled <[EMAIL PROTECTED]> writes: (repeat) I am developing a plugin which loads raw images from digital cameras (CRW,NEF etc). I might be wrong, but doesn't such a plug-in exist already? One exists for dcraw (Canon's raw format). Don't know if that would work on the other formats. Shouldn't we consider including that in the main distribution for 2.2, since that type of format is now more & more widespread? Who's the author? Cheers, Dave. ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Wording in German: Toolbox
On 26.07.2004, at 17:12, Roman Joost wrote: I was digging a bit around in the net to find out, which word is more used for the Toolbox: "Werkzeugfenster" or "Werkzeugkasten". The most tutorials I found are using "Werkzeugkasten", even Sven uses "Werkzeugkasten" in his book. But "Werkzeugfenster" is often more used in forums, when people try to describe a problem and they aren't familiar with The GIMP I prefer Werkzeugkasten simply because the window that is displaying the tools is not necessarily exclusively occupied by tools. Servus, Daniel PGP.sig Description: This is a digitally signed message part
[Gimp-developer] Re: [Gimp-docs] Wording in German: Toolbox
On Mon, Jul 26, 2004 at 05:31:28PM +0200, Sven Neumann wrote: > Hi, > > I am sure you already checked the german > glossary maintained by the GTP, didn't you? > Yep - and there is nothing in there. But i'll post my message as on gimp-i18n as well. Greetings, -- Roman Joost www: http://www.romanofski.de email: [EMAIL PROTECTED] signature.asc Description: Digital signature
[Gimp-developer] Re: [Gimp-docs] Wording in German: Toolbox
Hi, Roman Joost <[EMAIL PROTECTED]> writes: > This mail is for "translating" the Toolbox into German. I wasn't sure > how to translate the Toolbox to German for the manual. But > please, hold your breath and let me explain why. > > I was digging a bit around in the net to find out, which word is more > used for the Toolbox: "Werkzeugfenster" or "Werkzeugkasten". The most > tutorials I found are using "Werkzeugkasten", even Sven uses > "Werkzeugkasten" in his book. But "Werkzeugfenster" is often more used > in forums, when people try to describe a problem and they aren't > familiar with The GIMP. > > I spoke to Ellen to find out what she think. She said, that > "Werkzeugfenster" will be more descriptive. "Werkzeugkasten" is a bit > odd, because she have to think first, what I'm refering to. Thats > exactly my feeling. If I were a new user, "Werkzeugfenster" will be a more > descriptive word for the Toolbox than "Werkzeugkasten". But, maybe I'm > totally wrong and other may think of a completly different > window/dialog? > > So, what do you guys think: "Werkzeugfenster" or "Werkzeugkasten"? I suggest you bring this up on the gnome-i18n mailing-list. Other apps are most likely using this string as well and the best solution is to use a consistent translation. I am sure you already checked the german glossary maintained by the GTP, didn't you? Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Wording in German: Toolbox
Hi there, On Mon, Jul 26, 2004 at 05:12:37PM +0200, Roman Joost wrote: > So, what do you guys think: "Werkzeugfenster" or "Werkzeugkasten"? Let's vote! [ ] Werkzeugfenster [ ] Werkzeugkasten My vote goes for "Werkzeugfenster". Bye, Tino. signature.asc Description: Digital signature
[Gimp-developer] Wording in German: Toolbox
This mail is for "translating" the Toolbox into German. I wasn't sure how to translate the Toolbox to German for the manual. But please, hold your breath and let me explain why. I was digging a bit around in the net to find out, which word is more used for the Toolbox: "Werkzeugfenster" or "Werkzeugkasten". The most tutorials I found are using "Werkzeugkasten", even Sven uses "Werkzeugkasten" in his book. But "Werkzeugfenster" is often more used in forums, when people try to describe a problem and they aren't familiar with The GIMP. I spoke to Ellen to find out what she think. She said, that "Werkzeugfenster" will be more descriptive. "Werkzeugkasten" is a bit odd, because she have to think first, what I'm refering to. Thats exactly my feeling. If I were a new user, "Werkzeugfenster" will be a more descriptive word for the Toolbox than "Werkzeugkasten". But, maybe I'm totally wrong and other may think of a completly different window/dialog? So, what do you guys think: "Werkzeugfenster" or "Werkzeugkasten"? Thanks, -- Roman Joost www: http://www.romanofski.de email: [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: [Gimp-developer] 16 bit Gimp?
Hi, Sven Neumann wrote: > Joseph Heled <[EMAIL PROTECTED]> writes: > > (repeat) I am developing a plugin which loads raw images from digital > > cameras (CRW,NEF etc). > > I might be wrong, but doesn't such a plug-in exist already? One exists for dcraw (Canon's raw format). Don't know if that would work on the other formats. Shouldn't we consider including that in the main distribution for 2.2, since that type of format is now more & more widespread? Who's the author? Cheers, Dave. -- David Neary, Lyon, France E-Mail: [EMAIL PROTECTED] CV: http://dneary.free.fr/CV/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi, Dave Neary <[EMAIL PROTECTED]> writes: > This brings up an interesting question... is it possible to install a > plug-in in the user's directory, and have translations managed by > gettext? Where do the .mo files get installed in this case, and how can > one make gettext aware of them? This is all already handled. Just have a look at gimp-plugin-template or gimp-freetype. You can install everything but the actual plug-in executable into whatever prefix you specify. Not a very interesting question... Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Win32 compile troubles
Michael Schumacher wrote: /tmp/am4t7.308/traces.m4:1397: /bin/m4: Error matching regular expression "^ *\(.*\) *$" Use of uninitialized value in split at /bin/automake-1.7 line 5077, line 397. automake-1.7: no `Makefile.am' found or specified Try automake 1.8.5. It should built without problems on MinGW. I ran into a problem with automake-1.8.2 (which is the latest from the MinGW site), so it should be considered to require 1.8.5 on Win32. Upgrading to autoconf 2.59 and automake 1.8.5 did the trick, thanks. -- brion vibber (brion @ pobox.com) signature.asc Description: OpenPGP digital signature
Re: [Gimp-developer] Win32 compile troubles
Hi, Brion Vibber <[EMAIL PROTECTED]> writes: > I've been trying to compile Gimp on Win32 to confirm that my TWAIN > plugin patch for Mac OS X support won't break it on Windows. After > much fiddling I've managed to get 2.1.2 to compile and even run, but > automake craps out so I can't compile direct from CVS or get it to > update configure.in and the various Makefile.in's: > > > $ ./autogen.sh --prefix=/c/Brion/obj/gimp --disable-print > > I am testing that you have the required versions of libtool, autoconf, > automake, glib-gettextize and intltoolize. This test is not foolproof, > so if anything goes wrong, see the file HACKING for more information... > > Looks like Win32, you will need libtool 1.5 or newer. > > checking for libtool >= 1.5 ... yes (version 1.5) > checking for autoconf >= 2.54 ... yes (version 2.56) > checking for automake >= 1.6 ... yes (version 1.7.1) Please update to automake 1.7.9. Sorry, but attempting to compile gimp on win32 using such an outdated version automake seems silly. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] 16 bit Gimp?
Hi, Joseph Heled <[EMAIL PROTECTED]> writes: > (repeat) I am developing a plugin which loads raw images from digital > cameras (CRW,NEF etc). I might be wrong, but doesn't such a plug-in exist already? > There is actually lots of the functionality I need support (and some I > need to do) in the gimp already, if only the gimp was 16 bits ready. > > So, I wonder, any estimate how far in the future it is? We will start working on it as soon as 2.2 has been released. So that should be far enough away in the future for you not to wait on it. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Win32 compile troubles
> /tmp/am4t7.308/traces.m4:1397: /bin/m4: Error matching regular > expression "^ *\(.*\) *$" > Use of uninitialized value in split at /bin/automake-1.7 line 5077, > line 397. > automake-1.7: no `Makefile.am' found or specified > > > Googling the m4 error message turns up some chatter from circa 2002 > which recommends upgrading to the then-latest automake or m4... this is > automake 1.7.1 and GNU m4 1.4. GNU m4 1.4.1 came out recently, but it > won't compile with MinGW out of the box so I haven't tried that yet. > Has anyone had this problem, or worked around it, or not had it at all? > I'm compiling on Windows XP Home, with MinGW 3.1.0 and MSYS 1.0.10, the > various packages from Tor's page, and a few bits stuffed in from GnuWin32. Try automake 1.8.5. It should built without problems on MinGW. I ran into a problem with automake-1.8.2 (which is the latest from the MinGW site), so it should be considered to require 1.8.5 on Win32. HTH, Michael -- 250 MB Mailbox, 100 FreeSMS/Monat, 1000 MB Online-Festplatte Jetzt GMX TopMail kostenlos testen http://www.gmx.net/de/go/topmail ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-plugin-template: install
Hi, Quoting Sven Neumann <[EMAIL PROTECTED]>: > I don't think we should change this behaviour but we could very easily > add another install target (for example called install-user) that > installs the plug-in to the user's plug-in directory. This will only > work for a small subset of plug-ins though. Most plug-ins handled by a > gimp-plugin-template framework are complex plug-ins that install more > than just a single plug-in. Usually there will be help files, > translations, perhaps data files loaded at runtime. The extra > installation target may make people think that the plug-in has been > successfully installed with all its additional files while really only > the exectuable has been installed. I am not convinved that it would be > a good idea to do such a change. This brings up an interesting question... is it possible to install a plug-in in the user's directory, and have translations managed by gettext? Where do the .mo files get installed in this case, and how can one make gettext aware of them? Cheers, Dave. -- Dave Neary Lyon, France ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
