# Fortran Monthly Call: August 2022

**URL:** <https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120>\
**Category:** Uncategorized\
**Created:** [August 4, 2022, 10:29am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120 "2022-08-04T10:29:32Z")\
**Posts on this page:** 15\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [August 4, 2022, 10:29am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/1 "2022-08-04T10:29:32Z")

</div>

Dear all,

It’s again time to organise our next monthly call which will be in the week of **August 15-19** ; please see the following doodle poll to mark your availability:

### [Doodle: Fortran Monthly Call: August 2022](https://doodle.com/meeting/participate/id/bmwrwqAe)

The final time slot will be selected and announced on the evening (European time) of **Monday August 8, please complete the poll before then**.

If there are specific topics or issues you would like to raise, even if you are unable to attend the call, please post them in the thread here.

As usual, we will record this call and make it available online.

All the best,

Jeremie

---

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [August 11, 2022, 8:23am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/2 "2022-08-11T08:23:04Z")

</div>

Our next monthly call will be on **Tuesday, August 16 at 18:00 UTC**.

11:00 - 12:00 PDT (California)  
19:00 - 20:00 BST (London)  
20:00 - 21:00 CEST (Amsterdam)

As previously, the meeting will be recorded for those who cannot attend.  
Don’t hesitate to propose your items below.

---

<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:** [August 11, 2022, 9:02pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/3 "2022-08-11T21:02:03Z")

</div>

I would like to discuss the localization / translation of the webpage and similar resources.

---

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [August 11, 2022, 10:04pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/4 "2022-08-11T22:04:01Z")

</div>

Can we also include VS Code’s Modern Fortran into the localisation discussion?

---

<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:** [August 11, 2022, 10:09pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/5 "2022-08-11T22:09:36Z")

</div>

Can you provide any pointers to documentation on localization of VS Code extensions? I can have a look whether it is already possible to include those.

---

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [August 11, 2022, 10:12pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/6 "2022-08-11T22:12:52Z")

</div>

There is this active PR [Add Chinese Translation by quanzhuo · Pull Request #393 · fortran-lang/vscode-fortran-support · GitHub](https://github.com/fortran-lang/vscode-fortran-support/pull/393) that does some of the preliminary work for extension localisation.

- VS Code localisation general resource: [Visual Studio Code Display Language (Locale)](https://code.visualstudio.com/docs/getstarted/locales)
- VS Code sample extension using localisation: [vscode-extension-samples/i18n-sample at main · microsoft/vscode-extension-samples · GitHub](https://github.com/microsoft/vscode-extension-samples/tree/main/i18n-sample)
- SO post providing some additional info: [visual studio code - How to localise VSCode extension - Stack Overflow](https://stackoverflow.com/questions/56420338/how-to-localise-vscode-extension)

---

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [August 11, 2022, 10:52pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/7 "2022-08-11T22:52:58Z")

</div>

PS we probably need to scrap that PR and start a new one following the proper procedures

---

<div class="post-metadata">

**Author:** ![Ashwin](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/ashwin/32/1880_2.png) [@Ashwin](https://fortran-lang.discourse.group/u/Ashwin)\
**Post date:** [August 15, 2022, 10:36am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/8 "2022-08-15T10:36:21Z")

</div>

Hey all. This is the first time I’m joining a Monthly call. So how can I attend this?

---

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [August 15, 2022, 11:03am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/9 "2022-08-15T11:03:11Z")

</div>

We will post a Zoom link later today for people to join.

---

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [August 15, 2022, 11:04am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/10 "2022-08-15T11:04:38Z")

</div>

I would also like to discuss features to be included in Modern Fortran v4.0 [Version v4.0.0 · GitHub](https://github.com/fortran-lang/vscode-fortran-support/projects/5). Any thoughts, people have on the existing features and any additional features they wish to see.

---

<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:** [August 15, 2022, 3:54pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/11 "2022-08-15T15:54:49Z")

</div>

Here is the meeting information:

Time: Aug 16, 2022 06:00 PM Universal Time UTC  
Join Zoom Meeting: [Launch Meeting - Zoom](https://uni-bonn.zoom.us/j/62628777850?pwd=eWJPdENDRlFJZXF2UGVIZWhVZWdBQT09)

Meeting ID: 626 2877 7850  
Passcode: fortran

One tap mobile  
+496950500951,62628777850#,\*4627477# Germany  
+496950500952,62628777850#,\*4627477# Germany

---

<div class="post-metadata">

**Author:** ![jeremie.vandenplas](https://avatars.discourse-cdn.com/v4/letter/j/76d3ee/32.png) [@jeremie.vandenplas](https://fortran-lang.discourse.group/u/jeremie.vandenplas)\
**Post date:** [August 15, 2022, 5:47pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/12 "2022-08-15T17:47:21Z")

</div>

Welcome @Ashwin and thank you @awvwgk for the Zoom link.

Here is the current agenda:

1. Localization / translation of the Fortran-lang webpage (@awvwgk)
2. Localisation of the VS Code’s Modern Fortran (@gnikit)
3. New features for Modern Fortran v4.0? (@gnikit)

PS: I won’t be able to join the meeting tomorrow.

---

<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:** [August 16, 2022, 10:19am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/13 "2022-08-16T10:19:08Z")

</div>

If there is time I would like to discuss this issue:

> <https://github.com/fortran-lang/stdlib/issues/671>
>
> It would be useful to have a stdlib module for handling common file format for d…ata storage. If we can provide an interface in stdlib for this kind of operations we would make it much easier to integrate a new file format in a library which is already using stdlib.
> 
> This can be implemented in stdlib by pulling in common libraries used for this task, like JSON Fortran and TOML Fortran. Alternative, the interface could be declared in the specification and libraries like JSON Fortran and TOML Fortran can provide an implementation of \`stdlib\_json\` or \`stdlib\_toml\`, respectively.
> 
> \*\*Requirements\*\* (feel free to add to this list)
> 
> \- \[x\] map data structure
> \- \[\] list data structure
> \- \[\] date time derived type (for TOML)
> 
> \<details\>\<summary\>A possible API\</summary\>
> 
> \`\`\`f90
> !\> Standard library support for reading TOML documents
> module stdlib\_toml
> interface toml\_load
> !\> Load TOML data structure from file
> module subroutine toml\_load\_from\_file(filename, value, stat, message)
> !\> File name to read from
> character(\*), intent(in) :: filename
> !\> Data structure, either a built-in type a \[\[stdlib\_value::value\_type\]\]
> class(\*), allocatable, intent(out) :: value
> !\> Error code, if not provided routine will halt in case of error
> integer, intent(out), optional :: stat
> !\> Error message
> character(:), allocatable, intent(out), optional :: message
> end subroutine toml\_load\_from\_file
> end interface toml\_load
> 
> interface toml\_loads
> module subroutine toml\_load\_from\_string(string, value, stat, message)
> !\> File name to read from
> character(\*), intent(in) :: string
> !\> Data structure, either a built-in type or a \[\[stdlib\_value::value\_type\]\]
> class(\*), allocatable, intent(out) :: value
> !\> Error code, if not provided routine will halt in case of error
> integer, intent(out), optional :: stat
> !\> Error message
> character(:), allocatable, intent(out), optional :: message
> end subroutine toml\_load\_from\_string
> end interface toml\_loads
> end module stdlib\_toml
> \`\`\`
> 
> A similar interface would be provided for reading JSON to allow a consistent interface for all common IO formats.
> 
> \`\`\`f90
> !\> Standard library support for reading JSON documents
> module stdlib\_json
> interface json\_load
> !\> Load JSON data structure from file
> module subroutine json\_load\_from\_file(filename, value, stat, message)
> !\> File name to read from
> character(\*), intent(in) :: filename
> !\> Data structure, either a built-in type a \[\[stdlib\_value::value\_type\]\]
> class(\*), allocatable, intent(out) :: value
> !\> Error code, if not provided routine will halt in case of error
> integer, intent(out), optional :: stat
> !\> Error message
> character(:), allocatable, intent(out), optional :: message
> end subroutine json\_load\_from\_file
> end interface json\_load
> 
> interface json\_load
> !\> Load JSON data structure from string
> module subroutine json\_loads\_from\_string(string, value, stat, message)
> !\> File name to read from
> character(\*), intent(in) :: string
> !\> Data structure, either a built-in type or a \[\[stdlib\_value::value\_type\]\]
> class(\*), allocatable, intent(out) :: value
> !\> Error code, if not provided routine will halt in case of error
> integer, intent(out), optional :: stat
> !\> Error message
> character(:), allocatable, intent(out), optional :: message
> end subroutine json\_loads
> end interface json\_loads\_from\_string
> end module stdlib\_json
> \`\`\`
> \</details\>

Focusing on strategies to implement required data structures (lists, datetime, …) in stdlib in the near future as well as having stdlib specs with external implementations.

---

<div class="post-metadata">

**Author:** ![gnikit](https://yyz2.discourse-cdn.com/free1/user_avatar/fortran-lang.discourse.group/gnikit/32/1213_2.png) [@gnikit](https://fortran-lang.discourse.group/u/gnikit)\
**Post date:** [August 16, 2022, 1:25pm UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/14 "2022-08-16T13:25:37Z")

</div>

Yes, of course. The vscode stuff should not take long. There should be plenty of time left in the call.

---

<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:** [August 17, 2022, 9:23am UTC](https://fortran-lang.discourse.group/t/fortran-monthly-call-august-2022/4120/15 "2022-08-17T09:23:50Z")

</div>

Thanks to everybody participating in the discussion yesterday.

Recording is up at

[![](https://global.discourse-cdn.com/free1/uploads/fortran_lang/original/2X/2/28a5711d8cf8bd5b459a81d779626151a4b47d69.jpeg "Fortran Monthly Call: August 2022") ](https://www.youtube.com/watch?v=1l_a6YJuLwg)

I feel like we should make a banner which we can apply for the preview image on the recording.
