# Promoting Fortran in non-English languages

**URL:** <https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678>\
**Category:** Meta\
**Created:** [February 7, 2021, 8:03pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678 "2021-02-07T20:03:22Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![ivanpribec](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ivanpribec/32/3290_2.png) [@ivanpribec](https://fortran-lang.discourse.group/u/ivanpribec)\
**Post date:** [February 10, 2021, 9:48pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/41 "2021-02-10T21:48:49Z")

</div>

I consulted my Fortran notes in Slovenian. We used “tabela” as “array”. On Wikipedia I found covariant tensors as “kovariantni tenzor”. So I guess the most straightforward translation would be “ko-tabela” or “kotabela”.

In words such as cosine, or cotangent, and cosecant, the “co-” actually comes from _complementary_ (e.g. cosine = sine of the complementary angle).

With only 2.5 million Slovenian speakers worldwide, I don’t think I will invest the translation effort.

---

<div class="post-metadata">

**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\
**Post date:** [February 12, 2021, 3:18pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/42 "2021-02-12T15:18:23Z")

</div>

**I think I have found a treasure** 💰 !  
[https://translationproject.org/latest/gcc/fr.po](https://translationproject.org/latest/gcc/fr.po)  
That file contains the translations of gcc (including gfortran) messages in French. So I think I will just use _“co-tableau”_ for _“coarray”_… Using Google, I have found that term in two documents, that one and a french site.

Of course, for other languages, just use your language id, for example for Spanish:  
[https://translationproject.org/latest/gcc/es.po](https://translationproject.org/latest/gcc/es.po)

**You can see the list of the 19 available languages here:**  
[https://translationproject.org/latest/gcc/](https://translationproject.org/latest/gcc/)  
`be.po da.po de.po el.po es.po fi.po fr.po hr.po id.po ja.po nl.po ru.po sr.po sv.po tr.po uk.po vi.po zh_CN.po zh_TW.po`

---

<div class="post-metadata">

**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\
**Post date:** [February 14, 2021, 4:25pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/43 "2021-02-14T16:25:02Z")

</div>

First pass on the localization infrastructure is done. Feedback on the PR is very welcome, there is also side preview available, which in the best case is indifferent from the current fortran-lang webpage except for one additional line on each page, so (hopefully) not much to see yet.

---

<div class="post-metadata">

**Author:** ![msz59](https://avatars.discourse-cdn.com/v4/letter/m/3d9bf3/32.png) [@msz59](https://fortran-lang.discourse.group/u/msz59)\
**Post date:** [February 14, 2021, 4:56pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/44 "2021-02-14T16:56:35Z")

</div>

And how to get “there”? /pr/201 page just displays `English` in the last line. Changing preferred language to display pages in my Firefox does not take me anywhere else.

---

<div class="post-metadata">

**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\
**Post date:** [February 14, 2021, 5:21pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/45 "2021-02-14T17:21:00Z")

</div>

Sorry, discourse complained that the link was already present when I wrote the post, shouldn’t have listened. The PR is [here](https://github.com/fortran-lang/fortran-lang.org/pull/201), the preview at [Home - Fortran Programming Language](https://fortran-lang.org/pr/201/). I enabled only one language so far, as I said, not much to see yet.

If you want to test adding a translation have a look at

> <https://github.com/awvwgk/fortran-lang.org/blob/i18n/TRANSLATING.md>

You will need a local copy of the [`i18n`](https://github.com/awvwgk/fortran-lang.org/tree/i18n) branch from my fork for this, though.

---

<div class="post-metadata">

**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\
**Post date:** [February 18, 2021, 10:15pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/46 "2021-02-18T22:15:29Z")

</div>

The build preview of the fortran-lang has been updated with the French translation by @vmagnin at [Accueil - Le langage de programmation Fortran](https://fortran-lang.org/pr/201/fr/) and the Spanish translation by @alozada at [Inicio - Lenguaje de programación Fortran](https://fortran-lang.org/pr/201/es/). Please share your feedback here or at the [GitHub](https://github.com/fortran-lang/fortran-lang.org/pull/201).

---

<div class="post-metadata">

**Author:** ![m\_b\_metcalf](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@m\_b\_metcalf](https://fortran-lang.discourse.group/u/m_b_metcalf)\
**Post date:** [February 19, 2021, 8:55am UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/47 "2021-02-19T08:55:43Z")

</div>

FWIW, on my bookshelf I have Fortran books in French, German, Russian, Mandarin, Danish, and Japanese, so in those languages one is not starting from scratch. Three of these books, in German, Russian and Japanese, respectively, are translations done with my collaboration.

Below is a list, from 2004, of books on Fortran in languages other than English.

Regards,

Mike Metcalf

Chinese:

Programming Language Fortran 90 - He Xingui, Xu Zuyuan, Wu Qingbao and  
Chen Mingyuan, China Railway Publishing House, Beijing,  
ISBN 7-113-01788-6/TP.187, 1994.

Fortran 90 - Walter S. Brainerd, Charles H. Goldberg, Jeanne C. Adams,  
CHEP, Beijing and Springer, Berlin, 2000, ISBN 7-04-007937-2  
(a translation of Programmer’s Guide to Fortran 90).

Dutch:

Fortran 90 - W.S. Brainerd, Ch.H. Goldberg, and J.C. Adams, translated  
by J.M. den Haan, Academic Service, 1991, ISBN 90 6233 722 8.

Finnish:

Fortran 90/95 - Juha Haataja, Jussi Rahola and Juha Ruokolainen.  
Center for Scientific Computing (Finland), 2001, 3rd edition,  
ISBN 952-9821-60-3. WWW version: [http://www.csc.fi/oppaat/f95/](http://www.csc.fi/oppaat/f95/)

French:

Fortran 90; Approche par la Pratique - P. Lignelet, Série  
Informatique Éditions, Menton, 1993, ISBN 2-909615-01-4.

Fortran 90. Les concepts fondamentaux, the translation of “Fortran  
90 Explained” M. Metcalf, J. Reid, translated by M. Caillat and  
B. Pichon, AFNOR, 1993, Paris, ISBN 2-12-486513-7.

Fortran 90; Initiation à partir du Fortran 77 - Aberti, Série  
Informatique Éditions, Menton, 1992, ISBN 2-909615-00-6.

Les spécificités du Fortran 90, M. Dubesset et J. Vignes,  
Éditions Technip, 1993. ISBN 2-7108-0652-5.

Manuel complet du langage Fortran 90, et guide d’application,  
P. Lignelet, Série Informatique Éditions, 1995. ISBN 2-909615-02-2.

Manuel Complet du Langage Fortran 90 et Fortran 95, Calcul  
intensif et Génie Logiciel, P. Lignelet, Masson Éditions,  
Paris, 1996, ISBN: 2-225-85229-4.

Programmer en Fortran 90, C. Delannoy, Eyrolles, 1992,  
ISBN 2-212-08723-3.

Traitement des données numériques avec Fortran 90, M. Olagnon,  
Masson Éditions, 1996, ISBN 2-225-85259-6.

Structures des données (et leurs algorithmes) en Fortran 90/95,  
P. Lignelet, Masson Éditions, Paris, ISBN 2-225-85373-8.

German:

Fortran 90 Lehrbuch - D. Rabenstein, Hanser, 1995, ISBN 3-446-18235-7.

Die Programmiersprache F - W. Gehrke, Springer-Verlag, ISBN 3-540-63376-6.

Fortran 90 - B.Wojcieszynski and R.Wojcieszynski, Addison-Wesley, 1993,  
ISBN 3-89319-600-5.

Fortran 90: eine informelle Einführung - M. Heisterkamp,  
BI-Wissenschaftsverlag, 1991, ISBN 3-411-15321-0.

Fortran 90 Kurs: technisch orientiert - G. Schmitt, Oldenbourg,  
1996, ISBN 3-486-23896-5.

Fortran 90, Lehr- und Arbeitsbuch für das erfolgreiche Programmieren -  
W.S. Brainerd, C.H. Goldberg, and J.C. Adams, translated by P. Thomas  
and K. Paul, R. Olbenbourg Verlag, Muenchen, 1994, ISBN 3-486-22102-7.

Fortran 90 Lehr- und Handbuch - T. Michel, BI-Wissenschaftsverlag, 1994.

Fortran 90 Referenz-Handbuch: der neue Fortran-Standard - W. Gehrke,  
Carl Hansen Verlag, 1991, ISBN 3-446-16321-2.

Programmierung in Fortran 90 - Schobert, Oldenburg, 1991.

Programmierung mit Fortran 90 - Bäumer, Vieweg, Braunschweig, 1997,  
ISBN 3-528-05208-2.

Programmieren in Fortran - Erasmus Langer, Springer-Verlag, Wien,  
New York, 1993. ISBN 3-211-82446-4, 0-387-82446-4.

Software Entwicklung in Fortran 90 - Überhuber and Meditz, Springer  
Verlag, 1993, ISBN 0-387-82450-2.

Italian:

Some resources in Italian, including a manual, are at  
[http://space.tin.it/computer/gciabu](http://space.tin.it/computer/gciabu).

Japanese:

Fortran 90 Explained - Metcalf and Reid, translated by H. Nisimura,  
H. Wada, K. Nishimura, M. Takata, Kyoritsu Shuppan Co., Ltd., 1993,  
ISSN 0385-6984.

Russian

An Explanation of the Fortran 90 Programming Language (translation of  
Fortran 90 Explained - Metcalf and Reid), translated P. Gorbounov,  
Mir, Moscow, 1995, ISBN 5-03-001426-8. Available also from  
Petr.Gorbounov@cern.ch.

FORTRAN 77 to Fortran 90 Tutorial - Einarsson and Shokin, Russian  
Academy of Sciences, Novosibirsk, 1995, ISBN 5-85826-013-6.

Swedish

```
Fortran 90 - en introduktion - Blom, Studentlitteratur, Lund, 1994,
ISBN 91-44-47881-X.
```

---

<div class="post-metadata">

**Author:** ![Arjen](https://avatars.discourse-cdn.com/v4/letter/a/b9bd4f/32.png) [@Arjen](https://fortran-lang.discourse.group/u/Arjen)\
**Post date:** [February 19, 2021, 10:46am UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/48 "2021-02-19T10:46:39Z")

</div>

A bit vain perhaps, but my book Modern Fortran in Practice is available in a Russian translation.

---

<div class="post-metadata">

**Author:** ![alozada](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/alozada/32/298_2.png) [@alozada](https://fortran-lang.discourse.group/u/alozada)\
**Post date:** [February 22, 2021, 1:10pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/49 "2021-02-22T13:10:04Z")

</div>

For the Spanish translation.  
(Libre o gratuito)

In the section [Compilers](https://fortran-lang.org/compilers/), the section with more technicalities, the word “_free_” is used in the description of the GNU Fortran Compiler. Does this word refers to definition in [gnu.org](https://www.gnu.org/philosophy/free-sw.en.html) or means without paid?

---

<div class="post-metadata">

**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\
**Post date:** [February 22, 2021, 1:30pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/50 "2021-02-22T13:30:51Z")

</div>

I think it’s not only a translation problem.  
GCC is “FLOSS” = “Free/Libre and Open Source Software”  
See [FLOSS and FOSS - GNU Project - Free Software Foundation](https://www.gnu.org/philosophy/floss-and-foss.en.html)

---

<div class="post-metadata">

**Author:** ![tomohirodegawa](https://avatars.discourse-cdn.com/v4/letter/t/51bf81/32.png) [@tomohirodegawa](https://fortran-lang.discourse.group/u/tomohirodegawa)\
**Post date:** [May 15, 2021, 1:15pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/51 "2021-05-15T13:15:21Z")

</div>

Translation of [fortran-lang.org](http://fortran-lang.org) into Japanese is necessary for Japanese Fortran users, especially students, because many Japanese, including me, does not familiar with English.

Fortunately, the ISO Fortran standards (up to 2003) are translated into Japanese as the Japanese Industrial Standards, so translations of Fortran terminologies are not complicated.

As a result of searching “Fortran” on Google, [fortran-lang.org](http://fortran-lang.org) does not appear up to 100th place.  
Most of the information in Fortran in Japanese is older, so it would be beneficial for both the community and users to make this page appear at a top rank, in my opinion.

---

<div class="post-metadata">

**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\
**Post date:** [May 15, 2021, 5:28pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/52 "2021-05-15T17:28:21Z")

</div>

@tomohirodegawa  
the work on the internationalization of the site is paused. See:

> <https://github.com/fortran-lang/fortran-lang.org/pull/201>
>
> This patch introduces the infrastructure for localization support of the webpage… using the \[jekyll-multiple-languages-plugin\](https://github.com/kurtsson/jekyll-multiple-languages-plugin). You can checkout my \`i18n\` branch locally and add a new language as described in https://github.com/fortran-lang/fortran-lang.org/issues/197#issuecomment-775503384 to play around with the feature. Feedback is more than welcome on this patch.
> 
> \- \[x\] allow to replace page body with localized version
> \- \[x\] have markup only in main tree while translations provide content for page bodies
> \- \[x\] localize webpage title
> \- \[x\] localize all keywords in the main tree
> \- \[x\] localize all keywords in \`\_include\`
> \- \[x\] localize all keywords in \`\_layouts\`
> \- ~~localize permalinks~~
> \- \[x\] localize page names
> \- \[x\] avoid copying assets in every language subtree
> \- \[x\] include language navigation in footer
> \- \[x\] add documentation for translators
> 
> ~~This PR does not add localization to any language yet, a build preview will only show if nothing is broken.~~
> This pull request includes the Spanish translation provided by @aslozada and the French translation provided by @vmagnin, the side can be previewed at https://fortran-lang.org/pr/201/.

and @certik 's post:  
[https://fortran-lang.discourse.group/t/fortran-lang-is-now-second-in-google/931/21](https://fortran-lang.discourse.group/t/fortran-lang-is-now-second-in-google/931/21)

It will need a big effort and finding the right tool to manage the website, and you can participate to the discussion:  
[https://github.com/fortran-lang/fortran-lang.org/issues/89](https://github.com/fortran-lang/fortran-lang.org/issues/89)

In the meanwhile, what you can do to improve the ranking in search engines is to add content talking about the work of the Fortran community in your national web ecosystem:

- Review and revise the Japanese Wikipedia page (see [Reviewing all "Fortran" Wikipedia pages](https://fortran-lang.discourse.group/t/reviewing-all-fortran-wikipedia-pages/785)),
- and other Japanese wiki pages related to Fortran (for example, I have also entirely updated the [fortran [Wiki ubuntu-fr]](https://doc.ubuntu-fr.org/fortran) page),
- post messages into Japanese forums talking about computer languages,
- etc.

On the French side, [Fortran-log.org](http://Fortran-log.org) was invisible in Google but that kind of effort brought it to the 8th page. Not marvelous, but the more good quality content appear in your language with links toward that website, the more the ranking will improve. It needs work and patience.

---

<div class="post-metadata">

**Author:** ![tomohirodegawa](https://avatars.discourse-cdn.com/v4/letter/t/51bf81/32.png) [@tomohirodegawa](https://fortran-lang.discourse.group/u/tomohirodegawa)\
**Post date:** [May 16, 2021, 7:39am UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/54 "2021-05-16T07:39:58Z")

</div>

@vmagnin  
Thank you for letting me know the current status of internationalization.  
I already read a part of it, but I will follow the entire discussion.

> [@vmagnin](#):
>
> In the meanwhile, what you can do to improve the ranking in search engines is to add content talking about the work of the Fortran community in your national web ecosystem:
> 
> - Review and revise the Japanese Wikipedia page (see [Reviewing all “Fortran” Wikipedia pages](https://fortran-lang.discourse.group/t/reviewing-all-fortran-wikipedia-pages/785)),
> - and other Japanese wiki pages related to Fortran (for example, I have also entirely updated the [fortran [Wiki ubuntu-fr] ](https://doc.ubuntu-fr.org/fortran) page),
> - post messages into Japanese forums talking about computer languages,
> - etc.
> 
> On the French side, [Fortran-log.org](http://Fortran-log.org) was invisible in Google but that kind of effort brought it to the 8th page. Not marvelous, but the more good quality content appear in your language with links toward that website, the more the ranking will improve. It needs work and patience.

You showed me good points.  
I organized a modern Fortran local user group for a community of Japanese Fortran users and prepared a Slack channel.  
But I didn’t even think about modifying Wikipedia. I only use Fortran as an engineer in mechanical engineering. Maybe like many others, I don’t have enough knowledge to discuss Fortran comprehensively.  
There may be members in our community who are familiar with Fortran, so I would like to call for the formation of a task force for correcting Japanese Wikipedia articles.

To improve the quality of information written in Japanese related to Fortran, I have blogged several articles, including fpm, fprettify, FORD, and their integration with VSCode. I also self-published some books on Fortran entitled “practical object-oriented programming with Fortran,” “techniques for direct numerical simulations of aeroacoustics,” and “construction of a development environment for getting started with modern Fortran.”  
I continue this publishing activity and the community activities for the improvement.

@septc

> [@septc](#):
>
> I am wondering if it is useful to create a Discourse site also in Japanese, and put various links to this site (in addition to making their own forum/pages)? It might be helpful to “forward” unanswered questions or topics to different sites, for example, when more input or opinions are necessary. (But I am not sure whether it is possible to create a Discourse site for free…)

It is a good idea.  
Community members and I accept questions on Slack, but unfortunately, there are few questions. When the new academic year has begun, some students who started studying Fortran at university spit curses against Fortran on Twitter, so we respond individually…

---

<div class="post-metadata">

**Author:** ![themos](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/themos/32/521_2.png) [@themos](https://fortran-lang.discourse.group/u/themos)\
**Post date:** [May 16, 2021, 8:11am UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/55 "2021-05-16T08:11:50Z")

</div>

NAG is quite active in Japan and there are some resources in Japanese you can access, for instance: [Fortran Builder](https://www.nag-j.co.jp/nagfor/fb/index.htm)

---

<div class="post-metadata">

**Author:** ![vmagnin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/vmagnin/32/28_2.png) [@vmagnin](https://fortran-lang.discourse.group/u/vmagnin)\
**Post date:** [May 16, 2021, 10:56am UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/56 "2021-05-16T10:56:14Z")

</div>

@tomohirodegawa , that’s great, keep on the good work!

Concerning the Wikipedia national page, I have first entirely reorganized the text, verified and updated every link, updated the text with more recent information about modern Fortran, etc. Now, I am working in a more atomic style: when I learn something interesting in the Discourse about for example a new Fortran tool, I add one sentence with a link in the Wikipedia page.

That kind of atomic work is light but accumulates with time and improves the page. And verifying one by one all the links in the Wikipedia page can be a good point to start editing it: it’s useful for other people, you don’t need to be a Fortran expert, and sure you will learn many things by visiting those links…

---

<div class="post-metadata">

**Author:** ![Beliavsky](https://avatars.discourse-cdn.com/v4/letter/b/ba8739/32.png) [@Beliavsky](https://fortran-lang.discourse.group/u/Beliavsky)\
**Post date:** [May 16, 2021, 12:00pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/57 "2021-05-16T12:00:35Z")

</div>

> [@tomohirodegawa](#):
>
> @vmagnin  
> To improve the quality of information written in Japanese related to Fortran, I have blogged several articles, including fpm, fprettify, FORD, and their integration with VSCode. I also self-published some books on Fortran entitled “practical object-oriented programming with Fortran,” “techniques for direct numerical simulations of aeroacoustics,” and “construction of a development environment for getting started with modern Fortran.”  
> I continue this publishing activity and the community activities for the improvement.

Thanks for your efforts The Fortran Wiki has a [list](http://fortranwiki.org/fortran/show/Books) of books in English. Those familiar with the Fortran literature in other languages could add pages for those languages. Perhaps automated translations to English of some of the books above would be worthwhile.

On GitHub I sometimes see Fortran code with non-English comments. A tool that translated only comments to another language and left the code otherwise unchanged would be useful.

---

<div class="post-metadata">

**Author:** ![nbehrnd](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@nbehrnd](https://fortran-lang.discourse.group/u/nbehrnd)\
**Post date:** [May 16, 2021, 2:24pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/58 "2021-05-16T14:24:28Z")

</div>

> [@vmagnin](#):
>
> In this post, I talk about some simple ideas to promote Fortran and the work of our community in non-English languages.

@certik mentioned [earlier](https://fortran-lang.discourse.group/t/test-driven-training-pad/978/8) to prepare an ecosystem suitable to run Jupyter notebooks. Once these are set, a translation of them into languages other than English (as seen, e.g., with [learnlatex.org](https://www.learnlatex.org/)) may be one of the steps to achieve this goal.

---

<div class="post-metadata">

**Author:** ![certik](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/certik/32/4_2.png) [@certik](https://fortran-lang.discourse.group/u/certik)\
**Post date:** [May 16, 2021, 2:55pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/59 "2021-05-16T14:55:07Z")

</div>

> [@nbehrnd](#):
>
> @certik mentioned [earlier](https://fortran-lang.discourse.group/t/test-driven-training-pad/978/8) to prepare an ecosystem suitable to run Jupyter notebooks. Once these are set, a translation of them into languages other than English (as seen, e.g., with [learnlatex.org](https://www.learnlatex.org/)) may be one of the steps to achieve this goal.

Indeed.

I just want to say — I don’t want to be the one holding the translations efforts. I just think that unless we have a good technical solution as described above, the translations will be out of date and hard to manage. I don’t want to spread too thin to work on this, as I am 100% focusing on LFortran to deliver first.

So if we have enough dedicated people who will maintain translations by hand and commit to follow the master and make changes as needed (by hand), then I think we can have translations even now. But I am just warning that it’s a lot of work.

---

<div class="post-metadata">

**Author:** ![nbehrnd](https://avatars.discourse-cdn.com/v4/letter/n/e0b2c6/32.png) [@nbehrnd](https://fortran-lang.discourse.group/u/nbehrnd)\
**Post date:** [May 16, 2021, 3:36pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/60 "2021-05-16T15:36:12Z")

</div>

> [@certik](#):
>
> I just want to say — I don’t want to be the one holding the translations efforts.

This is understood. What I see with [learnlatex.org](http://learnlatex.org) is that the contributors share a consent about the most important topics, and the tools to be presented to a achieve a specific goal. Then there is explanatory text around the functions shown which is subject to translation. And – if deemed suitable – there are supplementary information beyond these core lessons (in case of the reference mentioned, the specifics to English [sic!], French, German, Català, etc.).

---

<div class="post-metadata">

**Author:** ![awvwgk](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/awvwgk/32/154_2.png) [@awvwgk](https://fortran-lang.discourse.group/u/awvwgk)\
**Post date:** [May 16, 2021, 4:31pm UTC](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678/61 "2021-05-16T16:31:00Z")

</div>

I have been working with sphinx for a while now to explore whether or not it is a viable alternative to jekyll. The advantage in sphinx would be that we have localization support through gettext via pybabel, which is a huge step up from what we can do in jekyll.

Reworking a complete webpage for a new static side generator is quite a task, but so far sphinx seems to offer everything we need to generate the fortran-lang webpage.

Here is a screenshot of the main page build with sphinx locally:

 ![image](https://global.discourse-cdn.com/free1/uploads/fortran_lang/original/1X/016b398eac9535c66e81ab075cdb34e7f30acb5b.png)

Not perfect though, but quite nice considering that I haven’t wrote a single line raw HTML for this result (the current jekyll main page is HTML + liquid templating). Sphinx provides some quite powerful mechanisms here, which allow to directly build page layouts with bootstrap CSS in restructuredtext or myst-markdown.

The localization would be done via po files generated by pybabel from rst and md sources, but I haven’t gotten to a point where I can seriously test this yet.

[Previous page](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678.md?page=2)

[Next page](https://fortran-lang.discourse.group/t/promoting-fortran-in-non-english-languages/678.md?page=4)
