Code block not parsed from Markdown

[nijel]

md2po seems to skip code blocks, but it makes sense to offer this for translation (for example, see WeblateOrg/weblate#10132).

Markdown:

**Network configuration**

All machines in our scenario are configured to use DNS and all of them have internet access. The initial entry point is nginx.example.com, which in our case can be reached from the internet. Your NGINX might reside behind a load balancer instead. To let the machines interoperate properly, consider the following inbound ports to be opened on your firewall:
    
    -   connections.internal.example.com:
        -   443 from nginx.example.com
        -   443 from cpmaster.internal.example.com
    -   cpmaster.internal.example.com:
        -   30301 from connections.internal.example.com \(Customizer\)
        -   30301 from nginx.example.com \(Customizer\)
        -   30098 from connections.internal.example.com \(Elasticsearch 7 – Connections 7 only\)
        -   30099 from connections.internal.example.com \(OpenSearch – Connections 7 or 8, Elasticsearch 5 – Connections 6.5 only\)
        -   32080 from connections.internal.example.com \(Ingress Controller\)
        -   31810 from connections.internal.example.com \(Microsoft Outlook add-in – Connections 7 only\)
    -   nginx.example.com:
        -   443 from everywhere
        -   80 from everywhere \(in case you plan to redirect to 443 and no load balancer does this job\)

PO file:

#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-10-10 13:18+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
"X-Generator: Translate Toolkit 3.10.0\n"

#: test.md%2Bp
msgid "**Network configuration**"
msgstr ""

#: test.md%2Bp
msgid ""
"All machines in our scenario are configured to use DNS and all of them have "
"internet access. The initial entry point is nginx.example.com, which in our "
"case can be reached from the internet. Your NGINX might reside behind a load "
"balancer instead. To let the machines interoperate properly, consider the "
"following inbound ports to be opened on your firewall:"
msgstr ""

[nijel]

@anderskaplan Do you recall if this was an intentional decision, or rather something that slipped?

[anderskaplan]

This was an intentional decision, based on the assumption that code blocks contain programming code, not intended for translation. That may not always be the case, as we can see here. So maybe it should be an option?

[nijel]

Parameters are currently tricky for Weblate, but we should eventually support that as well (see WeblateOrg/weblate#1897).

I think it's more expected to see all the content by default, even if something would not be translated.