<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Tyson,</p>
<p>
<blockquote type="cite">There are still some unmathced internal
links, but they were added to provide additional links to
related manual pages which I think should be useful.
</blockquote>
I recommend making merge requests to improve the source too, so
all languages of the Manual can benefit from it.</p>
<p>
<blockquote type="cite">However, there is one particular link type
I don't understand: `Word Word Word`_ (not :ref:`name`_).
</blockquote>
The Sphinx documentation has this in
<a class="moz-txt-link-freetext" href="https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-ref">https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-ref</a>
:</p>
<p>
<blockquote type="cite">Using <a class="reference internal"
href="https://www.sphinx-doc.org/en/master/usage/restructuredtext/roles.html#role-ref"
title="ref role"><code class="xref rst rst-role docutils
literal notranslate"><span class="pre">ref</span></code></a>
is advised over standard reStructuredText links to
sections (like <code class="docutils literal notranslate"><span
class="pre">`Section</span> <span class="pre">title`_</span></code>)
because it works across files, when
section headings are changed, will raise warnings if incorrect,
and works
for all builders that support cross-references.</blockquote>
So I suppose it is a less reliable version of :ref: for same-page
section linking. It might be a good idea to try replacing them in
the source with :ref:, but that's for another day...</p>
<p>This markup also seem to have another use, which is separated
link definition:
<a class="moz-txt-link-freetext" href="https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#external-links">https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#external-links</a><br>
</p>
<p>I am not exactly sure how section names references and glossary
terms are handled with translation. Usually leaving the original
in should be safe and Sphinx should substitute it with the
translated name. I also remember once using the translated name in
a :term: markup and it still worked. I guess in some cases you
really have to experiment to see how Sphinx like them.<br>
</p>
<p>Cheers,</p>
<p>Alvin Wong<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Tyson Tan 於 2/1/2022 15:39 寫道:<br>
</div>
<blockquote type="cite"
cite="mid:56d3ff733b1371fc955499982c06f109@tysontan.com">Hi Alvin,
<br>
<br>
Thank you for the information. I've fixed the broken markup errors
in zh_CN (yet to be built and sync). There are still some
unmathced internal links, but they were added to provide
additional links to related manual pages which I think should be
useful.
<br>
<br>
However, there is one particular link type I don't understand:
`Word Word Word`_ (not :ref:`name`_).
<br>
<br>
For example:
<br>
<br>
Dithering Threshold Modes
<br>
#: ../../reference_manual/filters/map.rst:82
<br>
Is the text of a link.
<br>
<br>
`Dithering Threshold Modes`_
<br>
#: ../../reference_manual/filters/map.rst:64
<br>
#: ../../reference_manual/filters/map.rst:98
<br>
Creates a link to map.rst:82 with the text of "Dithering Threshold
Modes".
<br>
<br>
Right now I've translated both of them, but I do wonder if I
should keep `Dithering Threshold Modes`_ untranslated?
<br>
<br>
Similarly:
<br>
<br>
:term:`keyframe`
<br>
#: ../../reference_manual/dockers/animation_curves.rst:56
<br>
This one I left it untouched, because I think it's an assigned
name, but I'm not sure.
<br>
<br>
:ref:`tablet_settings`
<br>
#: ../../KritaFAQ.rst:407
<br>
This one I also left untouched, without a doubt.
<br>
<br>
Thanks,
<br>
Tyson Tan
<br>
<br>
On 2022-01-02 01:17, Alvin Wong wrote:
<br>
<blockquote type="cite">Hi,
<br>
<br>
Thanks to all the translators who contributed to the
translations of
<br>
the Krita Manual! Here is something to help improve the
translations
<br>
further:
<br>
<br>
The docs.krita.org build produces warning output when it
encounters
<br>
markup issues, sometimes they may be caused by invalid RST
markup in
<br>
translations. We have made it so that it is a bit easier now to
check
<br>
the warning output for individual language builds. If you manage
or
<br>
contribute to the translations for the Krita Manual, please
check
<br>
these output messages.
<br>
<br>
You can check them by visiting
<br>
<a class="moz-txt-link-freetext" href="https://binary-factory.kde.org/job/Website_docs-krita-org/">https://binary-factory.kde.org/job/Website_docs-krita-org/</a>.
Under
<br>
"Last Successful Artifacts" (it may be collapsed, press "Expand
all"
<br>
to view), you may find files named `warnings-LANG.log`, where
LANG is
<br>
the language code of a translation. It contains a list of
warnings
<br>
produced when the Manual for the language is being built.
Translators
<br>
can check the relevant file to see if any translations are
causing
<br>
these warnings and try to fix them.
<br>
<br>
I understand these warnings can be hard to parse. I'll try to
explain
<br>
with two examples here to help understand them:
<br>
<br>
---
<br>
<br>
<br>
/home/user/workspace/Website_docs-krita-org/general_concepts/colors.rst:66:<translated>:1:
<br>
WARNING: Inline strong start-string without end-string.
<br>
<br>
The first part of the message shows a file path and line number.
In
<br>
this case it means the warning is related to the text in
<br>
`general_concepts/colors.rst` on line 66. `<translated>:1`
means the
<br>
issue is caused by the translated message. The translation can
be
<br>
found in `docs-krita-org_general_concepts__colors.po` (notice
that
<br>
`docs-krita-org_` is prepended to the path, slashes are replaced
by
<br>
three underscores `___`, and the file extension `.rst` is
replaced
<br>
with `.po`).
<br>
<br>
The warning message refers to a mismatched "strong" markup. In
RST the
<br>
markup uses double-asterisks `**`.
<br>
<br>
This is the relevant lines in the PO file:
<br>
<br>
#: ../../general_concepts/colors.rst:66
<br>
msgid ""
<br>
"There are other color models, like :ref:`model_lab`, where
we look at the"
<br>
"corresponding gray value of a color first, and then try to
describe it, not"
<br>
"it terms of hue and saturation, but by how red, green, blue,
and yellow it"
<br>
"is. Because our brains cannot really comprehend a color that
is both green"
<br>
"and red, or yellow and blue, this makes them good *polar
opposites* in a"
<br>
"sliding scale. We call this a **perceptual model**, as it is
based on how"
<br>
"*we see color instead of how the color is generated*."
<br>
msgstr ""
<br>
"Il y a d'autres modèles de couleurs, comme :ref:`model_lab`,
où nous"
<br>
"regardons tout d'abord, la valeur de gris correspondant à la
couleur et"
<br>
"ensuite, nous essayons de la décrire, non pas en termes de
teinte et de"
<br>
"saturation mais de combien de rouge, de vert, de bleu, de
jaune, elle est"
<br>
"composée. Puisque nos cerveaux ne peuvent pas réellement
appréhender une"
<br>
"couleur étant à la fois, vert et rouge ou jeune et bleu,
ceci en fait de"
<br>
"bons **opposés polaires* dans une échelle progressive. Ceci
est appelé un"
<br>
"*mode perceptuel*, puisqu'il repose sur la façon dont nous
voyons les"
<br>
"couleurs plutôt que comment une couleur est produite."
<br>
<br>
With sharp eyes you may notice the part `**opposés polaires*`
opens
<br>
with double-asterisks but closed with a single asterisk, which
is the
<br>
issue the warning message is referring to. The fix is to add
another
<br>
asterisk next to the closing asterisk.
<br>
<br>
---
<br>
<br>
<br>
/home/user/workspace/Website_docs-krita-org/general_concepts/colors/color_managed_workflow.rst:93:
<br>
WARNING: inconsistent term references in translated message.
<br>
original: [':ref:`here <profiling_and_calibration>`'],
translated: []
<br>
<br>
"Inconsistent term references" means the source message has
reference
<br>
links to another page or section, but the translated message is
<br>
missing them or is inconsistent with the source.
<br>
<br>
This is the lines in the PO file:
<br>
<br>
#:
../../general_concepts/colors/color_managed_workflow.rst:93
<br>
msgid ""
<br>
"Device spaces are those describing your monitor, and have to
be
<br>
made using a"
<br>
"little device that is called \"colorimeter\". This device,
in combination"
<br>
"with the right software, measures the strongest red, green
and blue your"
<br>
"screen can produce, as well as the white, black and gray it
produces. Using"
<br>
"these and several other measurements it creates an ICC
profile unique to"
<br>
"your screen. You set these in Krita's color management tab.
By default we"
<br>
"assume sRGB for screens, but it's very likely that your
screen
<br>
isn't exactly"
<br>
"fitting sRGB, especially if you have a high quality screen,
where it may be"
<br>
"a bigger space instead. Device spaces are also why you
should first consult"
<br>
"with your printer what profile they expect. Many printing
houses have their"
<br>
"own device profiles for their printers, or may prefer doing
color
<br>
conversion"
<br>
"themselves. You can read more about colorimeter usage
:ref:`here"
<br>
"<profiling_and_calibration>`."
<br>
msgstr ""
<br>
"Les espaces de périphériques sont ceux décrivant votre
écran. Ils doivent"
<br>
"être réalisés à l'aide d'un petit appareil appelé
« colorimètre ». Cet"
<br>
"appareil, associé au logiciel adéquat, mesure le rouge, le
vert et le bleu"
<br>
"les plus intenses que votre écran peut produire, ainsi que
le
<br>
blanc, le noir"
<br>
"et le gris qu'il produit. À partir de ces mesures et de
plusieurs
<br>
autres, il"
<br>
"crée un profil « ICC » spécifique à votre écran. Vous les
définissez dans"
<br>
"l'onglet de gestion des couleurs de Krita. Par défaut, nous
supposons"
<br>
"« sRGB » pour les écrans. Mais, il est très probable que
votre écran ne"
<br>
"corresponde pas exactement à « sRGB », surtout si vous avez
un écran de"
<br>
"haute qualité, qui peut posséder un espace plus grand. Les
espaces de"
<br>
"périphériques sont également la raison pour laquelle vous
devez d'abord"
<br>
"consulter votre imprimeur pour savoir quel profil il attend.
De nombreuses"
<br>
"imprimeries possèdent leurs propres profils de périphériques
pour leurs"
<br>
"imprimantes ou préfèrent effectuer elles-mêmes la conversion
des couleurs."
<br>
"Vous pouvez en savoir plus sur l'utilisation du colorimètre
:ref : « ici"
<br>
"<profilage_et_calibrage> »."
<br>
<br>
As you can see, the English source message has the reference
markup
<br>
":ref:`here <profiling_and_calibration>`", which was
mangled in the
<br>
translated message ":ref : « ici <profilage_et_calibrage>
»". The
<br>
correct markup can be ":ref:`« ici »
<profilage_et_calibrage>`" or "«
<br>
:ref:`ici <profilage_et_calibrage>` »" depending on the
wanted
<br>
outcome. Note the backticks and the positioning of whitespaces.
<br>
<br>
---
<br>
<br>
Here are some info on RST markup:
<br>
<a class="moz-txt-link-freetext" href="https://docs.krita.org/en/contributors_manual/krita_manual_conventions.html">https://docs.krita.org/en/contributors_manual/krita_manual_conventions.html</a>
<br>
<br>
If you need any help with fixing these errors, please don't
hesitate
<br>
to write to the mailing list, or ask in our chat, #krita on
<br>
Libera.Chat or <a class="moz-txt-link-freetext" href="https://webchat.kde.org/#/room/#krita:kde.org">https://webchat.kde.org/#/room/#krita:kde.org</a>
with
<br>
Matrix.
<br>
<br>
Thanks again for the hard work translating the Krita Manual! :)
<br>
<br>
Best Regards,
<br>
<br>
Alvin Wong
<br>
</blockquote>
</blockquote>
</body>
</html>