On Sun, Mar 8, 2020, 18:17 Tomasz Kłoczko <kloczko.tomasz@xxxxxxxxx> wrote:
On Sun, 8 Mar 2020 at 14:00, Ernestas Kulik <ekulik@xxxxxxxxxx> wrote:
[..]
> Are you involved with GNOME l10n? There is no need to do any of that
> with the way Damned Lies works.
No I'm not. Again this is not strict Gnome issue. This is why tooling
needs to be slightly adjusted/redesigned.
Did you ever try to check what I wrote? Seems not ..
You can do this by add in any spec file with meson build based
procedure by add in %build after "%meson_build" another line with
"%meson_build %{name}-update-po".
In case am/ac/lt based build procedures after "%make_build" you can
try to add line "%make_build -C po update-po".
In all those cases if after building package you will be able to see
that produced package size is different it will mean that distributed
.po files have *not been updated* before actual release.
Of course I haven’t tried it, because you’re not making any sense here. Define “updating PO files” first and then tell me why you are only pointing at GNOME if it’s a bigger issue.
Don't be surprised if you will find in few cases that final package
wit updating .po files will be slightly bigger (however in most of the
cases especially with enough long development history is possible to
see package size reductionist).
Less important is fact is will be enlargement or reduction. As long as
output after update is *different* it means that some additional work
on updating translations should be done.
Only small patches of all packages land like mate desktop packages are
with updated pot files and by this updated updating .po files does
not change final package size (but this is because mate developers
careers about that part of the development)
Nevertheless one more time: this issue is related more to tooling and
used currently methodologies so it stretches far beyond Gnome per se.
You are being way too vague about this. What is the size increase a consequence of? Do the actual strings in the PO files change? There’s a lot of meandering in that wall of text without actual content.
_______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
