Terminal commands for people like me fall under the amorphous category
of 'code' ;)
I'm good with the translation side though, thanks, I work in Virtaal
where we have a fairly massive TM by now.
Michael
06/02/2014 12:37, sgrìobh Alexandre Prokoudine:
There's nothing about code or programmin
On Thu, Feb 6, 2014 at 4:24 PM, Michael Bauer wrote:
> No, I didn't, thanks for mentioning it, I'm mostly a (very good) translator
> but not very good at code. There are a lot more people who are good at
> translating than people who can do both, sadly.
There's nothing about code or programming he
No, I didn't, thanks for mentioning it, I'm mostly a (very good)
translator but not very good at code. There are a lot more people who
are good at translating than people who can do both, sadly.
Michael
06/02/2014 11:51, sgrìobh Alexandre Prokoudine:
Yes, once the translation is there, it wil
On Thu, Feb 6, 2014 at 3:47 PM, Michael Bauer wrote:
>> Secondly, I wouldn't recommend translating master at all, unless you
>> enjoy doing your work twice :) The 2.8 branch, however, is perfect to
>> get your translation to actual users.
>
> Grrr that wasn't obvious but ok. If I commit to 2.8, is
06/02/2014 11:40, sgrìobh Alexandre Prokoudine:
Not that I know.
Pity but at least I know, thanks!
First of all, master == 2.10 :) There is no branch for 2.10 yet, and
there probably won't be any time soon.
Ok
Secondly, I wouldn't recommend translating master at all, unless you
enjoy doing
On Thu, Feb 6, 2014 at 3:30 PM, Michael Bauer wrote:
> Ok, thanks for the explanation. Are there plans/other people interested in
> making this happen?
Not that I know.
> I'm also still not sure about getting the new loc into 2.10 (if new locs can
> be added to minor versions) - currently the tr
Ok, thanks for the explanation. Are there plans/other people interested
in making this happen?
I'm also still not sure about getting the new loc into 2.10 (if new locs
can be added to minor versions) - currently the translations are sitting
in master - do I need to work on another file and/or
Or, to be more precise, there are no parsers to extract the text data that
is there and prepare it for gettext. Inkscape guys wrote such stuff for
e.g. GPL palettes, so it's possible to even translate colors. But we didn't
do that.
Alexandre
06 февр. 2014 г. 7:52 пользователь "Alexandre Prokoudine
Because these file formats have no extractable text data that could be put
into PO files.
It's possible to work around it, just not trivial.
Alexandre
06 февр. 2014 г. 5:13 пользователь "Michael Bauer"
написал:
> Hi João,
>
> That sounds really peculiar - why would these be untranslatable?
>
>
Hi João,
That sounds really peculiar - why would these be untranslatable?
Michael
05/02/2014 23:58, sgrìobh Joao S. O. Bueno:
Unfortunately names for GIMP resources - such as textures (patterns),
brushes, palettes, gradients are not internationalized, and are untranslatable.
On 4 February 2014 21:56, Michael Bauer wrote:
> Hi,
>
> Two questions - I've got the main UI translation for Gaelic (gd) at 97%
> (some strings I need to check in context) but I was wondering at this point
> what the process for getting a new locale into release is? Is it automatic
> or do I need
Hi,
Two questions - I've got the main UI translation for Gaelic (gd) at 97%
(some strings I need to check in context) but I was wondering at this
point what the process for getting a new locale into release is? Is it
automatic or do I need to file a bug and go through a release process?
The
12 matches
Mail list logo
