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: Tue, 05 Nov 2024 09:59:50 +0100 [thread overview]
Message-ID: <87v7x2vywp.fsf@pelzflorian.de> (raw)
In-Reply-To: <4462491730758010@mail.yandex.ru> (Krascovict Petrov's message of "Mon, 04 Nov 2024 19:08:31 -0300")
Krascovict Petrov <krascovict@yandex.ru> writes:
> I understand Florian Pelz, at first I will translate the texts, when I reach 100% translation I will test it on a virtual machine and do tests, thank
> you for the congratulations.
Yes, but I do recommend looking at Spanish or French for difficult,
ambiguous translations, particularly in some services’ ambiguous texts.
100% is a difficult goal for some of them, and correctness is more
important than having a translation. For example, you and other
translators frequently translated a graph from graph theory like
gráfico, or the /gnu/store store like loja (shop), which I then changed
to the word armazém from Guix’ Portuguese glossary.
Regards,
Florian
prev parent reply other threads:[~2024-11-05 9:00 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)
2024-11-04 22:08 ` Krascovict Petrov
2024-11-05 8:59 ` pelzflorian (Florian Pelz) [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87v7x2vywp.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.