Hi Rolf,
Rolf Bensch writes:
> Hi all again,
>
> Today I merged my German translations into master branch. Everybody
> still is invited to review my translation until July 31. Also after the
> new release will be out, of course.
Thanks.
> Please consider that new localization files may break
Hi all again,
Today I merged my German translations into master branch. Everybody
still is invited to review my translation until July 31. Also after the
new release will be out, of course.
Please consider that new localization files may break existing scanimage
scripts.
Hope this helps.
Hi Olaf,
It would be nice to see some tags in git, as reminder for the recent
stage in our release process.
This is just an idea for the discussion how to organize such things in
future.
Cheers,
Rolf
Am 24.07.19 um 14:35 schrieb Olaf Meeuwissen:
> Hi again all,
>
> Still following the release
Hi Ralph,
Ralph Little writes:
> Hi Olaf,I have create a branch and submitted a merge request for the
> en_GB translation. I notice that there is a "pipeline" error related
> to trailing white space generated from the GitLab machinery. I'm not
> sure what that signifies. I did another diff
Hi Olaf,I have create a branch and submitted a merge request for the en_GB
translation.
I notice that there is a "pipeline" error related to trailing white space
generated from the GitLab machinery.
I'm not sure what that signifies. I did another diff between the new and old
file, and there
Hi all,
Olaf Meeuwissen writes:
> [...]
> We now have a week to update translations as well. [...] Here are
> some stats, sorted by percentage of the strings that are translated.
> Translated Fuzzy Untranslated
>98.24% 0.75% 1.00%: nl.po
99.67% 0.00% 0.33%:
Hi Olaf,
I guess those are marked as fuzzy. The gettext tools will preseed
untranslated message strings based on "similar" translated strings.
Obviously, that sometimes leads to radically wrong translations.
These fuzzy strings will *not* be used at run-time. They are just
there in an attempt
Hi Ralph,
Ralph Little writes:
> Hi,I have grabbed to en_GB.po file and I have engaged the services of
> poedit to work through the texts.
Good.
> I have a few comments:
> 1) Some of the GB translations are obviously completely wrong. I
> assume that the original messages have radically change
Hi,Related to translations, I notice that there is no en_GB for xsane.If there
are no objections, I volunteer to create one and produce the necessary
transactions.
I have registered with GitLab and sent a request to join.
I have contributed some Canon scanner changes with Rolf in the past and
Hi,I have grabbed to en_GB.po file and I have engaged the services of poedit to
work through the texts.I have a few comments:
1) Some of the GB translations are obviously completely wrong. I assume that
the original messages have radically change from their original intentions.
2) Some of the
Hi,I don't mind having a look at en_GB.What is involved?
Cheers,Ralph
On Wednesday, July 24, 2019, 5:35:21 a.m. PDT, Olaf Meeuwissen
wrote:
Hi again all,
Still following the release schedule on our [1.0.28 milestone][1], our
master branch is now (2019-07-24 12:00UTC) in code freeze.
Hi again all,
Still following the release schedule on our [1.0.28 milestone][1], our
master branch is now (2019-07-24 12:00UTC) in code freeze. Please do
*not* push/merge to master unless it fixes
- hardware destroying bugs (no reports at present),
- compile failures (our CI is clean so we're
12 matches
Mail list logo
