We're using mdpo for the translation of the AntennaPod website. Now that we're getting in the first translations, we've noticed that newlines in tables are replaced with spaces when the PO(T) are created, and that this messes up the rendering of the table.
The following table:
| Key | Action |
| -- | -- |
|`P` | Play/Pause|
| `J`/`A`/`,` | Rewind media |
| `K`/`D`/`.` | Forward media |
| `+`/`W` | Raise media volume channel |
| `-`/`S` | Lower media volume channel) |
| `M` | Mute/unmute (toggle) media volume channel (only on Android 6 and higher) |
This, however, creates rendering issues like on this page (en correct, fr not).
I realise that tables are not (yet) part of Commonmark. But given that this actually is just a multiline string, I would expect (based on this article) the PO file to have \n instead of a space.
Would this be possible? Or is there an alternative solution that you can think of (e.g. structuring our MD table slightly differently)?
Your table is not correctly formatted because separators must have 3 characters or more, so the second line must be | --- | --- | instead of | -- | -- | to be properly parsed. Cheers!
Hello!
We're using
mdpo
for the translation of the AntennaPod website. Now that we're getting in the first translations, we've noticed that newlines in tables are replaced with spaces when the PO(T) are created, and that this messes up the rendering of the table.The following table:
when running
turns into
This, however, creates rendering issues like on this page (en correct, fr not).
I realise that tables are not (yet) part of Commonmark. But given that this actually is just a multiline string, I would expect (based on this article) the PO file to have
\n
instead of a space.Would this be possible? Or is there an alternative solution that you can think of (e.g. structuring our MD table slightly differently)?
Many thanks!