Git commit 74dbbd5feadd5a87d17d7b06178e4c77481499eb by Oliver Kellogg.
Committed on 25/03/2024 at 17:51.
Pushed by okellogg into branch 'master'.
Fix typo "ortography" -> "orthography"
* In lang/{nb,nn,sr}/rules rename ortography.rules to orthography.rules
* Globally change "ortography" to "orthography".
M +1-1doc/user/diffpatch.docbook
M +2-2doc/user/lingo.docbook
M +2-2doc/user/poformat.docbook
M +1-1doc/user/summit.docbook
M +1-1lang/nb/rules/CMakeLists.txt
R +1-1lang/nb/rules/orthography.rules [from:
lang/nb/rules/ortography.rules - 088% similarity]
M +1-1lang/nn/exclusion/README
M +1-1lang/nn/rules/CMakeLists.txt
R +1-1lang/nn/rules/orthography.rules [from:
lang/nn/rules/ortography.rules - 099% similarity]
M +1-1lang/sr/rules/CMakeLists.txt
R +1-1lang/sr/rules/orthography.rules [from:
lang/sr/rules/ortography.rules - 089% similarity]
M +2-2pology/lang/nb/exclusion.py
M +2-2pology/lang/nn/exclusion.py
M +1-1pology/lang/sr/nobr.py
M +1-1pology/proj/kde/header.py
https://invent.kde.org/sdk/pology/-/commit/74dbbd5feadd5a87d17d7b06178e4c77481499eb
diff --git a/doc/user/diffpatch.docbook b/doc/user/diffpatch.docbook
index 8fee02158..f5fd5edaf 100644
--- a/doc/user/diffpatch.docbook
+++ b/doc/user/diffpatch.docbook
@@ -990,7 +990,7 @@ Since the file of rejects is also an ediff PO, after edits
such as this to make
Embedding Patches
-Depending on the kind of text which is being translated, and distance
between the source and target language grammar, ortography, and style, it may
be difficult to review the ediff in isolation. In general, messages in ediff PO
file will lack positional context, which is in the full PO
provided by messages immediately preceding and following the observed message.
For example, a long passage from documentation probably needs no positional
context. But a short, newly added message such as "Crimson" could very well
need one, if it has neither msgctxt nor an extracted comment
describing it: is it really a color? what grammatical ending should it have (in
a language which matches adjective to noun gender)? Several messages around it
in the full PO file could easily show whether it is just another color in a
row, and their grammatical endings (determined by a translator earlier).
+Depending on the kind of text which is being translated, and distance
between the source and target language grammar, orthography, and style, it may
be difficult to review the ediff in isolation. In general, messages in ediff PO
file will lack positional context, which is in the full PO
provided by messages immediately preceding and following the observed message.
For example, a long passage from documentation probably needs no positional
context. But a short, newly added message such as "Crimson" could very well
need one, if it has neither msgctxt nor an extracted comment
describing it: is it really a color? what grammatical ending should it have (in
a language which matches adjective to noun gender)? Several messages around it
in the full PO file could easily show whether it is just another color in a
row, and their grammatical endings (determined by a translator earlier).
Another difficulty is when an ediff message needs some editing before
being applied. This may not be easy to do this directly in the ediff PO file.
Everything is fine so long as only the added text segments
({+...+}) are edited, but if the sentence needs to be
restructured more thoroughly, the reviewer would have to make sure to put all
additions into existing or new {+...+} segments, and to wrap
all removals as {-...-} segments. If this is not carefully
performed, the patch will not be applicable any more, as the old message
resolved from it will no longer exactly match a message in the target PO
file.
diff --git a/doc/user/lingo.docbook b/doc/user/lingo.docbook
index 4160c7138..57519585e 100644
--- a/doc/user/lingo.docbook
+++ b/doc/user/lingo.docbook
@@ -17,7 +17,7 @@
The first level is simply the "language". In linguistic sense this can
be a language proper (whatever that means), a dialect, a variant written in
different script, etc. Each language in this sense is assigned a code in
Pology, when first elements of support for that language are introduced. By
convention this code should be an http://en.wikipedia.org/wiki/ISO_639;>ISO 639 code (either two- or
three-digit) if applicable, but in principle can be anything. Another
convenient source of language codes is the GNU C library. For example,
Portugese language spoken in Portugal would have the code pt
(ISO 639) while Portugese spoken in Brazil would be pt_BR
(GNU C library).
-The second level of language-specificity is the "environment". In
linguistic terms this could be whatever distinct but minor variations in
vocabulary, style, tone, or ortography, which are specific to certain
