-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dutch translation / Nederlandse vertaling #42
Comments
Thanks, I have cloned the repository and had a quick look at the text - it
should not be too hard to produce a translation :).
|
For long sentences, I am using https://www.deepl.com/ to accelerate the work. I am very impressed by the result. I have just to verify the translation and change a few words or expressions. |
Interesting option. I have never used such a service before. I have started
the translation, but I found that sometimes I need to formulate things
differently to make it proper Dutch. For instance: "Learn about using ..."
- a literal translation is possible, but it feels clumsy, so I translated
it as: "How do you use ...". Oh well, perhaps my idiosyncratic usage of my
mother tongue :).
|
I changed wordings and formulations for the German translation as well, since the literal translation didn't really work nicely. |
@awvwgk @arjenmarkus But globally, I feel that DeepL, although not perfect, is a great help for long sentences and paragraphs. I will also have a look to those tools:
Anyway, when the first round of translation will be over, I plan to print everything and calmly read it, then improve it again when possible. I feel that a problem with translation is that you are focusing on a sentence or a paragraph, but it's difficult to keep in mind the whole picture... Finally, an interesting point in translating that doc is that I am learning new fpm features. That's could be a good argument to motivate other people. And it is a relatively easy way to be involved in the community: it's far easier to translate the doc of fpm than to try to contribute to its code, now that the tool is growing mature. The learning curve is far more gentle. |
I posted a few notes on my experience with GitHub's copilot in neovim for ML/AI based translation at #33. |
Something is off with the file encoding, I get
Also, could you apply the patch shown below to your branch to enable Dutch in the language navigation? diff --git a/Makefile b/Makefile
index 9044909..00c473d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# Minimal makefile for Sphinx documentation
# You can set these variables from the command line.
-LANGUAGES ?= en de zh_CN es fr
+LANGUAGES ?= en de zh_CN es fr nl
SPHINXOPTS ?=
SPHINXBUILD ?= sphinx-build
SPHINXINTL ?= sphinx-intl
diff --git a/pages/_templates/sbt-sidebar-footer.html b/pages/_templates/sbt-sidebar-footer.html
index 0c04530..d988c54 100644
--- a/pages/_templates/sbt-sidebar-footer.html
+++ b/pages/_templates/sbt-sidebar-footer.html
@@ -2,7 +2,7 @@
<div class="navbar_extra_footer">
<div class="sd-fs-6">
·
- {%- for lang in ('zh_CN', 'de', 'en', 'es', 'fr', ) %}
+ {%- for lang in ('zh_CN', 'de', 'en', 'es', 'fr', 'nl', ) %}
{%- if lang == language %}
<b>{{lang.lower()[-2:]}}</b>
{%- else %} |
Will do. Hm, the UTF-8 stuff is incorrect, that is something I will have to
look into as well (unless it has to do with my previous use of an e-trema
(looks like an e-umlaut) in extended ANSI
Op do 20 jan. 2022 om 17:55 schreef Sebastian Ehlert <
***@***.***>:
… Something is off with the file encoding, I get
...
Update: locale/de/LC_MESSAGES/how-to.po +1, -0
Update: locale/zh_CN/LC_MESSAGES/how-to.po +1, -0
Update: locale/es/LC_MESSAGES/how-to.po +1, -0
Update: locale/fr/LC_MESSAGES/how-to.po +1, -0
Traceback (most recent call last):
... several lines Python exception gibberish ...
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xeb in position 18: invalid continuation byte
Also, could you apply the patch shown below to your branch to enable Dutch
in the language navigation?
diff --git a/Makefile b/Makefile
index 9044909..00c473d 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# Minimal makefile for Sphinx documentation
# You can set these variables from the command line.
-LANGUAGES ?= en de zh_CN es fr
+LANGUAGES ?= en de zh_CN es fr nl
SPHINXOPTS ?=
SPHINXBUILD ?= sphinx-build
SPHINXINTL ?= sphinx-intl
diff --git a/pages/_templates/sbt-sidebar-footer.html b/pages/_templates/sbt-sidebar-footer.html
index 0c04530..d988c54 100644
--- a/pages/_templates/sbt-sidebar-footer.html
+++ b/pages/_templates/sbt-sidebar-footer.html
@@ -2,7 +2,7 @@
<div class="navbar_extra_footer">
<div class="sd-fs-6">
·
- {%- for lang in ('zh_CN', 'de', 'en', 'es', 'fr', ) %}
+ {%- for lang in ('zh_CN', 'de', 'en', 'es', 'fr', 'nl', ) %}
{%- if lang == language %}
<b>{{lang.lower()[-2:]}}</b>
{%- else %}
—
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN6YR5L2ZDENASCB54KPB3UXA467ANCNFSM5MIIBSSA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Might be, I can currently see something like this fpm-docs/locale/nl/LC_MESSAGES/how-to.po Line 158 in f5f7345
Which seems incorrectly encoded. Similarly for a few other places. Also, there seems to be a missing double quote at fpm-docs/locale/nl/LC_MESSAGES/how-to.po Lines 110 to 112 in f5f7345
|
I have completed a first version of the translation. Unfortunately, my
Cygwin system does not allow me to build a preview for reasons known only
to itself, but it claims a component of Sphinx is not installed, whereas
the Cygwin setup program claims it is available (sphinxcontrib.applehelp).
So I cannot proof-read the result.
Op do 20 jan. 2022 om 21:49 schreef Arjen Markus ***@***.***
…:
Oh, bugger - my favourite editor is working around the UTF-8 encoding. I
was naïve - sigh. No big problem now I am aware of this.
Op do 20 jan. 2022 om 20:42 schreef Sebastian Ehlert <
***@***.***>:
> Might be, I can currently see something like this
>
>
> https://github.com/fortran-lang/fpm-docs/blob/f5f7345bd0a7ae23e902103c5ac2e7cecef81006/locale/nl/LC_MESSAGES/how-to.po#L158
>
> Which seems incorrectly encoded. Similarly for a few other places.
>
> Also, there seems to be a missing double quote at
>
>
> https://github.com/fortran-lang/fpm-docs/blob/f5f7345bd0a7ae23e902103c5ac2e7cecef81006/locale/nl/LC_MESSAGES/how-to.po#L110-L112
>
> —
> Reply to this email directly, view it on GitHub
> <#42 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAN6YR7TSAB2ZQRRNQS4YFDUXBQRTANCNFSM5MIIBSSA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
I created a preview at https://awvwgk.github.io/fpm-docs/nl/index.html |
Thanks - I will have a look!
Op ma 24 jan. 2022 om 10:16 schreef Sebastian Ehlert <
***@***.***>:
… I created a preview at https://awvwgk.github.io/fpm-docs/nl/index.html
—
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN6YR5E2K4BCEGOQLXQDZDUXUKFXANCNFSM5MIIBSSA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Well, there is definitely room for improvement :)
Op ma 24 jan. 2022 om 10:57 schreef Arjen Markus ***@***.***
…:
Thanks - I will have a look!
Op ma 24 jan. 2022 om 10:16 schreef Sebastian Ehlert <
***@***.***>:
> I created a preview at https://awvwgk.github.io/fpm-docs/nl/index.html
>
> —
> Reply to this email directly, view it on GitHub
> <#42 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAN6YR5E2K4BCEGOQLXQDZDUXUKFXANCNFSM5MIIBSSA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
I updated the Dutch preview again, since there was a new commit on your branch. Regarding your question on the Note header, those will be used in the admonition headers like on the landing page. |
Ah, thanks. I have no time today to add my corrections and look at the
current results, but I should have an opportunity tomorrow
Op wo 26 jan. 2022 om 16:15 schreef Sebastian Ehlert <
***@***.***>:
… I updated the Dutch preview again.
Regarding your question on the *Note* header, those will be used in the
admonition headers like on the landing page.
—
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN6YR3KZOCQI3UM7GR5EOTUYAFXXANCNFSM5MIIBSSA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Okay, I made the corrections. I also noticed that the text "Browse
tutorials" and others in the index page are not translated at all, even
though translations are available.
Op wo 26 jan. 2022 om 16:19 schreef Arjen Markus ***@***.***
…:
Ah, thanks. I have no time today to add my corrections and look at the
current results, but I should have an opportunity tomorrow
Op wo 26 jan. 2022 om 16:15 schreef Sebastian Ehlert <
***@***.***>:
> I updated the Dutch preview again.
>
> Regarding your question on the *Note* header, those will be used in the
> admonition headers like on the landing page.
>
> —
> Reply to this email directly, view it on GitHub
> <#42 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAN6YR3KZOCQI3UM7GR5EOTUYAFXXANCNFSM5MIIBSSA>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
There is a bug in sphinx-design which does not allow proper translation of the button labels. I haven't found a fix for this issue yet. |
See #39 (comment) |
Thanks for this comment. Well, I will not try and figure that one out. At
the very least the strings that should replace them are there.
Op zo 30 jan. 2022 om 12:23 schreef Vincent Magnin ***@***.***
…:
See #39 (comment)
<#39 (comment)>
—
Reply to this email directly, view it on GitHub
<#42 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAN6YR45PTL7PHY7T4MSXE3UYUNRRANCNFSM5MIIBSSA>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
This thread tracks the translation of the documentation to Dutch. Feel free to post either in Dutch or English in this threads, whatever seems most appropriate.
cc @arjenmarkus
The text was updated successfully, but these errors were encountered: