On Sat, Mar 22, 2025 at 06:32:54PM +, Helge Kreutzmann wrote:
Am Wed, Mar 19, 2025 at 09:44:47AM +0100 schrieb Marc Haber:
tl;dr: New Wiki Page https://wiki.debian.org/I18n/ForPackageMaintainers,
please review
I just did it. I usually updated it right away, but at one or two
points it is m
On Tue, 25 Mar 2025 21:26:05 +, Bill Allombert
wrote:
>Le Tue, Mar 11, 2025 at 12:03:51PM +0100, Marc Haber a écrit :
>> tl;dr: We need more docs about best practices to handle translations as
>> a package maintainer
>
>I would suggest you find someone on debian-i18n willing to handle transla
Le Tue, Mar 11, 2025 at 12:03:51PM +0100, Marc Haber a écrit :
> tl;dr: We need more docs about best practices to handle translations as
> a package maintainer
I would suggest you find someone on debian-i18n willing to handle translations
for
adduser for you and give them commit access.
That is
On Mon, Mar 24, 2025 at 06:33:19PM +, Helge Kreutzmann wrote:
Am Mon, Mar 24, 2025 at 05:49:40PM +0100 schrieb Marc Haber:
"Using no line numbers" => invoke msgmerge with --no-location?
Yes.
"Web pages mentioned above" => I don't see web pages being mentioned. That
needs a name or a link
On Wed, 19 Mar 2025 15:05:56 +0100, Dirk Lehmann
wrote:
>I have a bit played around with `msgmerge` and found a way to display
>a `diff` which contains the translations which will be destroyed if
>you merge a .po file from a translator
>
> * test-de_DE-transl.po
>
>into your maintained one
>
>
Hello Marc,
Am Mon, Mar 24, 2025 at 05:49:40PM +0100 schrieb Marc Haber:
> On Sat, Mar 22, 2025 at 06:32:54PM +, Helge Kreutzmann wrote:
> > Am Wed, Mar 19, 2025 at 09:44:47AM +0100 schrieb Marc Haber:
> > If you have any questions on my changes it is probably best to discuss
> > this on list.
Hello Marc,
Am Wed, Mar 19, 2025 at 09:44:47AM +0100 schrieb Marc Haber:
> tl;dr: New Wiki Page https://wiki.debian.org/I18n/ForPackageMaintainers,
> please review
I just did it. I usually updated it right away, but at one or two
points it is more like a discussion. And due to my changes some
redu
On Tue, Mar 18, 2025 at 09:06:35PM +0100, Marc Haber wrote:
xgettext comes with a ton of options to help you. Have a look at the
diff I've attached for what I've been able to do.
Will do and take your suggestions. But it is still a wrapper needed.
I have put this into the adduser wrapper and
Hey Marc,
On 3/11/25 12:03 PM, Marc Haber wrote:
Basically the same applies for this step than for the POT generation
step, with the additional hardship that the PO files are generated,
being written to by a program AND STILL contain a significant part of
human work. I never know how much work o
Le 2025-03-18 18:19, Marc Haber a écrit :
In a few cases there is spurious "fuzzing", e.g. when the source
message uses `...' for quoting where it shoud have been using \"...\".
In some of these cases it may be possible to fix the issue in the
source message, but I believe other cases are actu
On Wed, 19 Mar 2025 10:46:32 +0100, Julien Plissonneau Duquène
wrote:
>Don't take it personally: as an established maintainer
>of i18nized software did you know about this process?
No, I didn't. I am arrogant enough to expect that relevant docs are
easy to find and in English. I had four years o
tl;dr: New Wiki Page https://wiki.debian.org/I18n/ForPackageMaintainers,
please review
Hi,
On Tue, Mar 11, 2025 at 12:03:51PM +0100, Marc Haber wrote:
Whenever I am angry about something in Debian, I start writing docs. So
I try this here, but here I don't know enough to be really helpful. I
h
Hi,
On Wed, Mar 12, 2025 at 01:06:11PM +0800, Maytham Alsudany wrote:
It might also be worthwhile to forward your message to
debian-i18n@l.d.o, since translators and i18n people are more likely to
be subscribed there and less likely to be subscribed here.
I didn't do that on purpose because th
On Wed, Mar 12, 2025 at 11:36:27AM +0100, Julien Plissonneau Duquène wrote:
Le 2025-03-11 12:03, Marc Haber a écrit :
(2)
There is some point in the development process when it is time to ask
for translations. Translators need a POT file which contains all the
translatable strings, and they make
On Tue, Mar 11, 2025 at 10:10:51PM +0900, Simon Richter wrote:
I'm on mobile, so only a quick reply: merging should be done with
msgmerge as well — you need to call it twice, once with the po files
from both branches, and once again with the pot file to fix all the
location comments and fuzzy f
On Wed, Mar 12, 2025 at 11:35:16AM +0100, Julien Plissonneau Duquène wrote:
Le 2025-03-12 03:03, Dirk Lehmann a écrit :
As I understand your question about a general workflow of translations
in all your email-cases correct, I think the short answer maybe to use
`quilt` to patch the .PO files ins
Hi,
Le 2025-03-11 12:03, Marc Haber a écrit :
Especially when one uses version control
Having recently worked on a (not yet mergeable as it depends on another
MR) update of the french translation of devscripts and already bracing
for the incoming pain as it's likely that I will have to rebas
Hi Dirk,
Le 2025-03-12 03:03, Dirk Lehmann a écrit :
As I understand your question about a general workflow of translations
in all your email-cases correct, I think the short answer maybe to use
`quilt` to patch the .PO files instead of committing them directly via
Git. Also consider `gbp-pq`,
Hi Marc,
Here are some of my thoughts based on my (relatively little) experience
with both translating to Arabic and receiving translations.
It might also be worthwhile to forward your message to
debian-i18n@l.d.o, since translators and i18n people are more likely to
be subscribed there and less
Hello Marc,
I am currently new as Debian Maintainer, but I have more experience
from upstream-side.
As I understand your question about a general workflow of translations
in all your email-cases correct, I think the short answer maybe to use
`quilt` to patch the .PO files instead of committing t
Hi,
I'm on mobile, so only a quick reply: merging should be done with msgmerge as
well — you need to call it twice, once with the po files from both branches,
and once again with the pot file to fix all the location comments and fuzzy
flags.
Alternatively, you can define a filter in git to rem
tl;dr: We need more docs about best practices to handle translations as
a package maintainer
My fellow developers,
there are two things in being a DD that I truly despise. The one is
keeping the machine readable debian/copyright up to date, the other is
handling of translations, regardless of
22 matches
Mail list logo
