string freeze in CVS, translators are invited

For te 0.22 target a string freez seems now appropriate.
There is 
not much happen beside functional bugfixes until a release.

Some plug-ins where i18n activated lately and some changed.
So it is a 
good idea to check all translations.

With the gtk2 build option it makes now even more sense to
translate as 
gtk2 supports the UTF-8 codeset.

Hartmut and I are keeping the german po files up to date.


The reason leading to the recent gtk2 support was it's i18n
support. Even 
if it has many drawbacks in gtk2, I'd like to disable i18n
for gtk1 
builds. Gtk1 would remain the most stable workhorse, just in
english.

Distributors fixed independently gtk1. So it is a very
confused situation.
The gtk maintainers dont try to fix the situation or make
clear why not. 
I think they try to enforce gtk2 with broken compatibility,
which makes 
FLTK even a better choice.
Technically I found no way to detect if which codeset to
use. So it is not 
easily possibly to workaround the situation.


Hope to hear from new and old translators 

Kai-Uwe Behrmann
                                + development for color
management 
                                + imaging / panoramas
                                + email: ku.bgmx.de
                                + http://www.behrmann.name


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys -
and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Kai-Uwe,

> Distributors fixed independently gtk1. So it is a very
confused situation.
> The gtk maintainers dont try to fix the situation or
make clear why not. 

GTK1 is officially deprecated by gtk.org. They don't want us
to use it. 
The only active GTK1 project is GTK+OSX.

> I think they try to enforce gtk2 with broken
compatibility, which makes 
> FLTK even a better choice.

I'm sure I agree FLTK is better for us than GTK2, but what
do you mean 
by "enforce gtk2 with broken compatibility"?

> Technically I found no way to detect if which codeset
to use. 

To detect in code between GTK1 and GTK2 would happen by
setting a flag 
at the autotools level and using ifdef in the code.

Thank you,

Robin
--
CinePaint.org

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys -
and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

> The reason leading to the recent gtk2 support was it's
i18n support. Even 
> if it has many drawbacks in gtk2, I'd like to disable
i18n for gtk1 
> builds. Gtk1 would remain the most stable workhorse,
just in english.

This is a very good idea.  I would second what others have
said about
GTK2, outside of i18n it is not necessarily an upgrade.

Regards,

Brad Hare



------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys -
and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Am 30.11.06, 11:28 -0800 schrieb Robin Rowe:

> > I think they try to enforce gtk2 with broken
compatibility, which makes 
> > FLTK even a better choice.
> 
> I'm sure I agree FLTK is better for us than GTK2, but
what do you mean 
> by "enforce gtk2 with broken compatibility"?

In my view a gtk1 release would have helped a lot. But they
argue to do no 
release and dont like to see the name GTK used at all for a
1.2.11 .
Why so bullminded not maintaining?
 
> > Technically I found no way to detect if which
codeset to use. 
> 
> To detect in code between GTK1 and GTK2 would happen by
setting a flag 
> at the autotools level and using ifdef in the code.

On some systems gtk1 ones displays fine with code latin1 for
german 
(SuSE). Others need! UTF-8 (Debian). This seems miraculous
deep in the gtk 
configuration. Can this been detected by autotools? How.

regards
Kai-Uwe Behrmann
                                + development for color
management 
                                + imaging / panoramas
                                + email: ku.bgmx.de
                                + http://www.behrmann.name


------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys -
and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers

Kai-Uwe,

> In my view a gtk1 release would have helped a lot. But
they argue to do no 
> release and dont like to see the name GTK used at all
for a 1.2.11 .
> Why so bullminded not maintaining?

I spent months trying to get GTK1-for-Windows stable. I can
understand 
completely why nobody likes working on this codebase. It's
huge and full 
of casts. The puzzle is why anyone would want to work on
GTK2.

> On some systems gtk1 ones displays fine with code
latin1 for german 
> (SuSE). Others need! UTF-8 (Debian). This seems
miraculous deep in the gtk 
> configuration. Can this been detected by autotools?
How.

To answer that specifically I'd need to know exactly what
needs to be 
installed on Debian to make latin1 work there. Any source
file can be 
detected by autotools by writing a test main that executes
during 
./configure. CinePaint does that for OpenEXR.

Robin
--
CinePaint.org

------------------------------------------------------------
-------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the
chance to share your
opinions on IT & business topics through brief surveys -
and earn cash
http://www.techsay.com/default.
php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Cinepaint-developers mailing list
Cinepaint-developerslists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ci
nepaint-developers