POt update script issues

[abu baniaz]

When running the pot update script, the issues in the attachment are reported. Is it possible these can be addressed?

[Huevos]

I answered that last time you asked.

translated_string = _("Our friend %s is %s years old.") % ('Abu', '50')

Change to this:

translated_string = _("Our friend %(person)s is %(age)s years old.") % {"person": 'Abu', "age": '50'}

[birdman]

What has caused this change?

Python is still happy with the first format, which exists all over enigma2.

[Huevos]

What has caused this change?

Python is still happy with the first format, which exists all over enigma2.

Ok, then you don't seem to understand what the warning is for.

If I want to change the order of variable_one and variable_two in the translated output it is impossible in the first case.

[birdman]

Ok, then you don't seem to understand what the warning is for.

I understand what it means.
However, since the translation files only refer to the text in _() calls, something must have changed to start producing these messages now

If I want to change the order of variable_one and variable_two in the translated output it is impossible in the first case.

As in:
The %{colour} %{shape}

becoming, in French

Le %{shape} ${colour}

[Huevos]

I understand what it means.
However, since the translation files only refer to the text in _() calls, something must have changed to start producing these messages now

As in:
The %{colour} %{shape}

becoming, in French

Le %{shape} $colour}

Nothing has changed. Abu is referring to the shell script which can be used to produce the *.po files. That script has always raised these warnings.

[birdman]

It's occurred to me (overnight) that there are probably few, if any, instances in Vix where having named args (for multiple arg striungs) would matter.

Either these parameters are numbers (where I would expect the same order to obtain) or they are strings, in which case that actual parameter values need to be localized too.

The %{colour} %{shape} example would need to be:

"The %{colour} %{shape}" % { 'colour', _(colour), 'shape': _(shape) }

with the po file containing translations for all potential colours and shapes. Does Vix do that?

[Huevos]

"The %{colour} %{shape}" % { 'colour', _(colour), 'shape': _(shape) }

It needs to be:

_("The %(colour)s %(shape)s") % { 'colour': _(colour), 'shape': _(shape) }

And yes that is valid. Do we use it? Probably not yet.

But here you have a problem:

_(shape)

There you are translating a variable. From where are you going to harvest the value of that variable to populate the pot file?

[birdman]

But here you have a problem:

_(shape)

There you are translating a variable. From where are you going to harvest the value of that variable to populate the pot file?

No. You are translating the value of a variable...
So you would need translations of square, triangle, circle ... - all values that shape might take. And you would need to know what those possibilities are.

[Huevos]

So how are you going to harvest them?

[birdman]

So how are you going to harvest them?

You can't. There is no information in the code about what the values might be.

[Huevos]

Well what is the point feeding them through gettext if they are not in the po file?

On the other hand...
https://github.com/OpenViX/enigma2/b...ns/Menu.py#L94
Here they are translatable because they are harvested from the xml.

[abu baniaz]

The objective is to be able to update the po files on GitHub so people can work on them from there. Getting them from receiver is not the best option. As an example, I uploaded all the latest ones from an updated image, somebody else worked on the one on his box and took the file back.

An example commit to resolve the issue from PLi is here:
https://github.com/OpenPLi/enigma2/p...f4856067f03afa

[birdman]

....with the po file containing translations for all potential colours and shapes. Does Vix do that?

It occurs to me that it's a bit worse than that.
French (German, Latin, ...) has gender for adjectives, so you'd need to have a male and female version of blue (bleu, bleue) and the same for all other colours, in all languages, even when they are the same. You'd also need a plural version for each, too (bleus).

[Huevos]

An example commit to resolve the issue from PLi is here:
https://github.com/OpenPLi/enigma2/p...f4856067f03afa

I already posted that solution above.