Pull request on github is ready. It contains only fixes in glade file. I
decided to include translation fixes in my branch with updating ru.po
2014-04-21 23:57 GMT+04:00 John Ralls :
>
> On Apr 21, 2014, at 12:48 PM, Dmitry Pavlov wrote:
>
> > I would prefer to make a number of pull requests:
>
Am Sonntag, 13. April 2014, 08:07:10 schrieb John Ralls:
> On Apr 13, 2014, at 2:16 AM, Dmitry Pavlov wrote:
> > I've found that to implement minimum solution, we can just add
> > context="..." to glade translated labels. like this
> > Every
> >
> > This utilizes context lookup feature in gettext
On Apr 21, 2014, at 12:48 PM, Dmitry Pavlov wrote:
> I would prefer to make a number of pull requests:
> 1. Adding context to labels
> 2. Updating all translations with new file pot file.
> 3. String translations for ru.po
>
> Maybe it is reasonable to merge 1 & 2 into one set of commits that
I would prefer to make a number of pull requests:
1. Adding context to labels
2. Updating all translations with new file pot file.
3. String translations for ru.po
Maybe it is reasonable to merge 1 & 2 into one set of commits that will
form single pull request?
What about target branch? May be i
On Apr 21, 2014, at 12:10 PM, Dmitry Pavlov wrote:
> Currently those are all the strings I wanted to change. For other strings
> there are no problems with translation.
> The main problem with "every" and friends occurred because controls was
> embedded in "sentence", that consisted of a set
Currently those are all the strings I wanted to change. For other strings
there are no problems with translation.
The main problem with "every" and friends occurred because controls was
embedded in "sentence", that consisted of a set of labels.
The work is still in progress and there 650 fuzzy st
On Apr 21, 2014, at 10:26 AM, Dmitry Pavlov wrote:
> Yes, I added "context" attribute to labels in xml file and after pot file
> regeneration this market strings in po file has additional msgctxt lines.
>
> I can't imagine how that change can affect c or scheme code as it was static
> labels.
Yes, I added "context" attribute to labels in xml file and after pot file
regeneration this market strings in po file has additional msgctxt lines.
I can't imagine how that change can affect c or scheme code as it was
static labels.
21.04.2014 20:18 пользователь "John Ralls" написал:
>
> On Apr
On Apr 20, 2014, at 12:55 PM, Dmitry Pavlov wrote:
> Sorry for delay: here is the branch:
> https://github.com/zeldigas/gnucash/tree/scheduled_i18n_fix
> Last commit contains planned changes. To minimize diff I applied updated pot
> file only for ru.po (most other po are outdated, so there was
Sorry for delay: here is the branch:
https://github.com/zeldigas/gnucash/tree/scheduled_i18n_fix
Last commit contains planned changes. To minimize diff I applied updated
pot file only for ru.po (most other po are outdated, so there was a lot of
changed lines).
I'd be glad if someone could check the
On Apr 15, 2014, at 7:18 AM, Dmitry Pavlov wrote:
> If I create branch from maint head and make necessary changes, can you review
> them, if fits for current minimum libs version reqs. for gnucash?
>
Of course.
Regards,
John Ralls
___
gnucash-dev
If I create branch from maint head and make necessary changes, can you
review them, if fits for current minimum libs version reqs. for gnucash?
2014-04-13 23:05 GMT+04:00 Dmitry Pavlov :
> If I get you right, you'd like to know what is the difference between
> using this context (or disambiguati
If I get you right, you'd like to know what is the difference between using
this context (or disambiguation prefixes) and plural functions. The main
difference is dynamic UI updates. With plurals you need to update labels
around the inputs on every change of spinbox or combobox. Even if that
update
On Apr 13, 2014, at 2:16 AM, Dmitry Pavlov wrote:
> I've found that to implement minimum solution, we can just add
> context="..." to glade translated labels. like this
> Every
>
> This utilizes context lookup feature in gettext, instead of disambiguation
> prefixes, but it seems working just f
I've found that to implement minimum solution, we can just add
context="..." to glade translated labels. like this
Every
This utilizes context lookup feature in gettext, instead of disambiguation
prefixes, but it seems working just fine.
does anyone mind about such change?
2014-04-13 12:48 GMT+
Hello, I have a suggestion that can help improve translation for some
languages.
So here is the problem: in src/gnome-utils/gtkbuilder/gnc-frequency.glade,
that describe a form for filling in transaction schedule, translation
string "Every" is used for all possible combination - for daily, weekly,
16 matches
Mail list logo