What about translation of fityk?
I want to translate it in Russian very much.
Is it any automatic builtin localisation system (like gettext) in fityk or patching
source code (replacing English phrases with Russian) is only working method now?
If so, i will do it (bacause i have necessity in localisation, not just
for me).
And sorry for my English )
On Sun, May 18, 2008 at 4:03 PM, ss23 <ss...@mail.ru> wrote:
> What about translation of fityk?
> I want to translate it in Russian very much.
> Is it any automatic builtin localisation system (like gettext) in fityk
no, and it's not planned, because maintaining translations takes time
> or patching
> source code (replacing English phrases with Russian) is only working method now?
yes
> If so, i will do it (bacause i have necessity in localisation, not just
> for me).
If you really have to do it, you can do it, but think also about other
options. For example, you can write a tutorial in Russian how to use
it, that to load file one has to select "Load File", etc.
I think you will have more problems with this translation than it's worth.
Best,
Marcin
--
Marcin Wojdyr | http://www.unipress.waw.pl/~wojdyr/
Hi!
no, and it's not planned, because maintaining translations takes time
On Sun, May 18, 2008 at 4:03 PM, ss23 <ss...@mail.ru> wrote:
> What about translation of fityk?
> I want to translate it in Russian very much.
> Is it any automatic builtin localisation system (like gettext) in fityk
yes
> or patching
> source code (replacing English phrases with Russian) is only working method now?
Yes, but it's harder than just maintaining one version, and I don't
have time to do it.
I see, you use wxT() utf-macros with GUI-strings (const wxChar * wxT(const char *s)).
And, as i understood, everything that we need, its to replace this macros with _() .
See:
http://docs.wxwidgets.org/stable/wx_stringfunctions.html#wxgettranslation
We can define, for example, our macros _FITYK() and define it like _():
#define _FITYK() _()
We wiil use _FITYK() with strings, that must be translated.
With this method, we can restore previous code with defining it back to
wxT() evetytime with:
#define _FITYK() wxT()
What do you think?
Yes, I know.
>
> What do you think?
I'm sorry, but I'm not interested in int'lization of fityk.
It's possible to gettext-tize it, but it's hard to predict what
problems will it cause (problems with building, packaging, not updated
translations, different lengths of strings can break layout, etc.),
and I don't think it will be useful for many people.
Cheers,