unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: Krascovict Petrov <krascovict@yandex.ru>
Cc: "74190@debbugs.gnu.org" <74190@debbugs.gnu.org>
Subject: [bug#74190] [PATCH 0/3] install: Enable pt_BR translation.
Date: Mon, 04 Nov 2024 08:52:41 +0100	[thread overview]
Message-ID: <87cyjbo2pi.fsf@pelzflorian.de> (raw)
In-Reply-To: <26101730666097@mail.yandex.ru> (Krascovict Petrov's message of "Sun, 03 Nov 2024 17:37:48 -0300")

Hello Krascovict and thank you for translating.

Note that I do not speak Portuguese.

Krascovict Petrov <krascovict@yandex.ru> writes:
> In this case I am in doubt about translations of functions (inside the
> parentheses) whether they can be translated or not?

Generally no, but you can look at the string in Weblate in other
languages like Spanish or French.  See if they have translated it.
For example, if a variable name is defined with (define), in a few
cases, it is possible to translate it, but it must be translated
everywhere the same way.

Alternatively you would have to test in Guix if it works.

Regards,
Florian




  reply	other threads:[~2024-11-04  7:53 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-03 15:14 [bug#74190] [PATCH 0/3] install: Enable pt_BR translation Florian Pelz
2024-11-03 15:25 ` [bug#74190] [PATCH 1/3] install: Open info manuals that have region codes Florian Pelz
2024-11-03 15:25 ` [bug#74190] [PATCH 2/3] install: Change the territory when we have learned it Florian Pelz
2024-11-03 15:25 ` [bug#74190] [PATCH 3/3] gnu: info-reader: Inherit from texinfo-7 Florian Pelz
2024-11-03 20:37 ` [bug#74190] [PATCH 0/3] install: Enable pt_BR translation Krascovict Petrov
2024-11-04  7:52   ` pelzflorian (Florian Pelz) [this message]
2024-11-04 22:08     ` Krascovict Petrov
2024-11-05  8:59       ` pelzflorian (Florian Pelz)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cyjbo2pi.fsf@pelzflorian.de \
    --to=pelzflorian@pelzflorian.de \
    --cc=74190@debbugs.gnu.org \
    --cc=krascovict@yandex.ru \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).