gemmaro

This is off-topic to the issue title, but I've noticed code blocks can also start with `>vim` (followed by a line end). Currently, only `>` is supported (ref. [example](https://github.com/vim/vim/blob/04cc8975930b7b2c5d6753d3eddf57dab2816518/runtime/doc/helphelp.txt#L253)).

> Also there is codeblock [splitting](https://github.com/mquinson/po4a/blob/5d16870f490fbb0ca15c2bc11c0a4a5ffebf2d5a/lib/Locale/Po4a/VimHelp.pm#L279) into several paragraphes. Is it actually desirable? Hello @Fat-Zer, are you currently working on this? If you find it beneficial, please feel free to...

@Fat-Zer Thanks for the update. Since textwidth was removed, it seems the issue is resolved. I should have mentioned in #570, as just referencing the issue might not have been...

@Fat-Zer Ah, so the po4a release is fast approaching. I read the post on lists.po4a.org. If that’s the case, then there’s no need to rush this change in right now....

@mquinson Thank you for taking the time to review the pull request. I don't have any specific plans to make further changes at this time. However, I have some reservations...

I updated the 'STATUS OF THIS MODULE' section in SimplePod based on your suggestion. I also added the SimplePod module to the list of translation targets.

The test seems to fail at the moment. `perl Build.PL` to generate the `Build` file, and `./Build test --test_files=t/charset.t` to run the added tests (or without the option for full...

While the text module can be used at the moment, managing elements like headers, footers, and indentations can be cumbersome. A dedicated parser for the RFC format would provide the...

> I tried to translate the text from the **RFC 5322**. Apparently, the **gettextization** of the text ('text' format) was successfully. However, the RFC 5322 in particular, and all the...

> The translation of "transfer" might be "移動" in the context of "rubygems.org," but "転送" is also fine. Thank you for your review! I’ll apply your suggestion after I get...