Hello,
you can find the Italian debconf translation in the attachment.
Cheers,

Hello Andrej,
I intend to NMU matrix-synapse early January 2025 to fix longstanding l10n
bugs[1]. The changelog would be something like the following:

 matrix-synapse (1.116.0-4+nmu1) unstable; urgency=medium

   * Non-maintainer upload.
   * Update debconf template translation
     - Spanish translation.
       Thanks to Camaleón (Closes: #987593)
     - Italian translation.
       Thanks to Ceppo (Closes: #1019159)

Please tell me if you are currently preparing a new release yourself
and would like me to skip the NMU.

Greetings

         Helge

Hi,

Please submit a merge request on Salsa.
Thanks.

Hello Andrej,
Am Sun, Dec 01, 2024 at 02:16:05PM +0100 schrieb Andrej Shadura:

Is there a HOWTO do this?

Otherwise, I noticed that you added several debconf translations in
version 1.121.0-4, it is exactly the same for Spanish and Italian.

Greetings

         Helge

Hello,

I don’t know, probably. I’m not sure where to find it, though.

You see, that’s *exactly* why I asked you to submit a merge request :) That would help me to remember to get them merged.

Hello Andrej,
Am Tue, Jan 07, 2025 at 07:17:08PM +0100 schrieb Andrej Shadura:

Well, I'm not very well versed with that workflow, so figuring this out
would require substantial ressources.
(just in case):

Step 1: Download the attachement from #987593 (as es.po) and #1019159
        (as it.po)

Step 2: Store those two files in debian/po

Step 3: Add the two debian/changelog entries:
        * Add Spanish debconf template translation. (Closes: #987593)
	* Add Italian debconf template translation. (Closes: #1019159)

Step 4: Upload

I hope this helps …

Greetings

          Helge

Hello,

It would however simplify the process of contributing to many other packages as well.

I know the procedure. And I know about the BTS. However, I don’t always check the BTS before uploading. And also if you’re prepared to do an NMU, submitting a MR is just one step more, and would save me some work.

Hello Andrej,
Am Tue, Jan 07, 2025 at 07:28:57PM +0100 schrieb Andrej Shadura:

Possibly. But "saves me work" applies to me as well.

My aim is to get translations in where the maintainers are unable to
do so or do not care. Both does not apply to you (as your last upload
shows).

My preprations is exactly the e-mail I send you (and a test build to
see that the package does not FTBFS, which I could not resolve). I
would do exactly the steps I wrote.

But I'm not a TOOD list manager, and checking the BTS while preparing
an upload is IMHO a good practice, at least I do this for my packages.

Given this, I hope you can manage to remember to prepare an upload
with those two translations included (for the sake of the respective
users), but I'm not working on this package anymore, rather on those
were the need is larger.

Greetings

            Helge

Here [1] is the official documentation for creating merge requests.  You will have
to have registered for salsa access, and I'm not sure if there's any way to avoid
using a web browser for that one-time task. The workflow requires either having push
access to the remote repository, or to "create a fork" of the repository in your
own gitlab namespace (another one-off task that you'll probably need to do in the UI).

If you do not want to use the web UI for the actual MR creation, you can instead
create the merge request when you push to upstream [2] (I use this in my workflow).
I've had trouble with setting the text of the MR, but I'm sure I'm escaping something
incorrectly in my script.

Best,
Antonio Russo

[1] https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html
[2] https://docs.gitlab.com/ee/topics/git/commit.html#push-options-for-merge-requests