mån 2003-03-03 klockan 19.57 skrev Raphaël Quinet:
c. Why a dpi *AND* a Pixels/inch setting? The bottom set,
with the Pixels/inch options menu should be enough. DPI
should be part of the text header for this frame.
Because you want to be able to set the default unit? I
fre 2003-02-28 klockan 18.28 skrev [EMAIL PROTECTED]:
http://bugzilla.gnome.org/show_bug.cgi?id=79751
Oops, this is certainly not something you told me about ever.
The bug activity log for this report (available as a link from the
page) very clearly shows that [EMAIL PROTECTED] added a
Currently, the packages for the GNOME Fifth Toe release is being brought
together at the http://5toe.lyrical.net/ site, where package maintainers
can nominate their software for inclusion. Fifth Toe is, for those that
don't know, a collection of nice additional software that works with
GNOME.
sön 2003-02-02 klockan 19.49 skrev Sven Neumann:
Christian Rose [EMAIL PROTECTED] writes:
Currently, the packages for the GNOME Fifth Toe release is being brought
together at the http://5toe.lyrical.net/ site, where package maintainers
can nominate their software for inclusion. Fifth Toe
Recently many messages in gimp have been changed to append %s, like
in this example:
#: app/tools/transform_options.c:223
#, c-format
msgid Keep Height %s
The %s seems to be filled in with the return value of a call to
gimp_get_mod_name_control ().
What's the purpose of these changes to the
tor 2002-11-28 klockan 00.32 skrev David Weeks:
Robin,
I called you right the first time.
David,
please keep childish name-calling rants like this for yourself. Thanks.
Kind regards,
Christian
___
Gimp-developer mailing list
[EMAIL PROTECTED]
mån 2002-11-18 klockan 14.09 skrev jay.yan:
http://www.gimp.org/devel_cvs.html tells me that I can get the latest
code from cvs server via: cvs -z3 co gimp
and also it says:
There are also several branches in the GIMP cvs tree: the main or HEAD
branch is GIMP 1.3 (the development
On 6 Jun 2002, Sven Neumann wrote:
After a complete gimp clean (find . -name gimp -exec rm {};)
on my machine and new cvs get -z3 it still gets the old version
of the file gimpunits.c. But only that file is old. Other files
like Changelog are up to date.
I think it's time to write
ons 2002-06-05 klockan 23.28 skrev Philip Brown:
This is as good a point to ask as any; in following the
latest incarnation of the crazy dep-chain I ran into a
dead-end finding the mysterious 'fontconfig' (fontconfig
is needed by pango is needed by gtk2 is needed by gimp).
Anyone know
On Wed, 29 May 2002, David Neary wrote:
Hmmm... This is bad, because this is not compatible with the GPL. So we
must either stop distributing these files or distribute them in a separate
package that is not GPL'ed.
Why is giving credit to an author incompatible with the GPL?
It's not
lör 2002-05-04 klockan 18.10 skrev Sven Neumann:
* what will be the impact on the translations when we start using these?
translations will break and need to be updated. However I don't see
any particular problem here. Of course translators need to put some
thoughts into the mnemonics they
fre 2002-05-03 klockan 22.37 skrev Sven Neumann:
- If you are a translator or would like to help with translations,
check http://sven.gimp.org/1.2/i18n.html to see if your language
needs work.
Hmm, if you want to make sure that all translators get this info, then
it perhaps should be
Correct. My error. Sorry.
Christian
lör 2002-05-04 klockan 01.57 skrev Sven Neumann:
Hmm, if you want to make sure that all translators get this info, then
it perhaps should be sent to [EMAIL PROTECTED] too.
IIRC, I've sent a mail announcing the 1.2.4 release to gnome-i18n list
a few
lör 2002-02-16 klockan 06.59 skrev Marco Lamberto:
Zoom In + [Yes, changed, a bit more logical, no?]
Zoom Out-
If you have an US keyboard you'll notice that while the minus - is immediatly
accessible, the plus + is obtained by pressing Shift +
tis 2002-01-22 klockan 08.25 skrev Rebecca J. Walter:
Is the message reorganization in gimp HEAD completed? There are quite a
few changes, and I'd like to know if it's more safe to start translating
these without too many expected radical changes coming.
Nope. I'm not done yet. The
Is the message reorganization in gimp HEAD completed? There are quite a
few changes, and I'd like to know if it's more safe to start translating
these without too many expected radical changes coming.
Before anyone reminds me I'd like to state that I know, and am fully
aware of the fact that
Rebecca J. Walter wrote:
Just to warn everyone before translators start freaking out at Sven, I
am proofreading all original strings in the head branch of GIMP CVS. I
don't know how long this will take me. I will send out another mail
when I am mostly done. While this should improve future
Christian Rose wrote:
So when translators next work on translations, don't blame mitch and
sven for all the fuzzies. It should result in improvements and easier
translations in the future. (Plus translating head is discouraged
anyway).
If anyone wants to whine about this, whine
Replying to myself since I forgot some things...
Christian Rose wrote:
While enforcing the use of UTF-8 solves the encodings problem, it is not
feasible for many other reasons. One is simply the lack of support in
many editors and many other text processing tools (and terminals and so
Daniel Egger wrote:
Also, one important drawback of keeping all translations in one file in
CVS, and forcing translators to edit this file, is that it gets almost
impossible to verify the integrity of translations. As a translator and
creator and maintainer of the translation, I feel that
Daniel Egger wrote:
Whatever the solution regarding GIMP tips turns out to be, translators
want to be able to translate them from within po files. I hope everyone
has agreed on that :)
not really.
Okay, but that really makes you an exception among translators. This
discussion isn't new,
Daniel Egger wrote:
Why should I have to use a special XML editor?
You don't have to, that's the trick.
Ok, I got the impression from your message that this was the case.
How does the editor know what language I want to edit,
Easy, you tell it.
So this is an extra step that I have
Daniel Egger wrote:
I think you need to
consider the experience that menthos has with this situation. If we
consider what we might end up with in the future (many more tips, more
complicated tips, more languages), it makes sense to plan po right now.
I'm never planning for now but
pcg@goof.com ( Marc) (A.) (Lehmann ) wrote:
Native support for UTF-8 is uncommon and of course that is bad and
Sorry? my mailer supports it (mutt) my editor supports it (vim), my terminal
supports it (xterm), my irc-client supports it (epic), my browser(s) suipport
it (lynx, netscape,
Sven Neumann wrote:
Hmm, would it be possible to make GIMP tips translatable in a po file in
the future? That would probably ease translation, since gettext has some
nice features: it's easy to compare the original message and the
translation, easy to spot messages that changed or new
Daniel Egger wrote:
No, as you say, a header file is probably the easiest solution,
Actually if there was an XML parser this would be the simplest solution.
It is just that we'd need a parser and I haven't evaluated the GMarkup
part of the new glib yet.
Ok.
there is probably no need
Sven Neumann wrote:
It isn't up to you as the program maintainer to merge translations
from STABLE to HEAD or something like that. Provide hints how
translators might proceed, but please don't change contents of the
files.
I have always asked people not to touch po files in CVS HEAD
R.I.P. Deaddog wrote:
I myself would probably convert the sv.po in Gimp HEAD to UTF-8, like in
GTK+, if I was kindly asked to, and it was recommended, but I still
don't want others to touch the PO file.
I think I could live with having to run iconv back and forward every
time I touch
Sven Neumann wrote:
I have always asked people not to touch po files in CVS HEAD at all.
Until we change this rule, the po files are in the maintainers
responsibility.
I do not agree.
Committing PO files to HEAD in any project is always risky business
(large frequent changes im
This is a rather separate thread, so I'm replying to it seperately.
Sven Neumann wrote:
For the HEAD branch, we should try to find a responsible translation
maintainer for each language. The language maintainer should have CVS
commit access and is responsible for coordinating his/her
30 matches
Mail list logo
