[5.0.x L10n Installation and Upgrade Guide] SHOWSTOPPER for Simplified Chinese. Does not build correctly without manual tweaking of one file.

[ptinley-vt]

Formatting breaks in this book due to an anomaly in translations/zh_CN/modules/installation-and-upgrade/pages/container-deployment/suma/proxy-deployment-suma.adoc

There are two locations in the file that break the formatting.

All pages after page 33 will have corrupt formatting and the books will be unreadable.
See below:

The string that breaks the formatting is circled.
All the text in the green boxes should be normal para text. (Well most of it).

To manually fix this go to:
Line 182. Add a line-break after '例如：' and before '----'
&
Line 317. Add a line-break after '例如：' and before '----'

Will look like this when correct.
Location 1

Location 2

[jcayouette]

Fixed in a local checkout of manager-5.0. Looks like we have to adapt to using some proper syntax. Testing a build now .

For example blocks we must use a single line break and I decided to use a source and language identifier.

Example Blocks (Code listings)

=== Configure Custom Persistent Storage

This step is optional.
However, if custom persistent storage is required for your infrastructure, use the [command]``mgr-storage-proxy`` tool.
This tool simplifies creating the container storage and Squid cache volumes.

Use the command in the following manner:

[source,shell]
----
mgr-storage-proxy <storage-disk-device>
----

For example:

[source, shell]
----
mgr-storage-proxy /dev/nvme1n1
----

For more information, type:

[source, shell]
----
mgr-storage-proxy --help
----

For consistent concatenation we must use the following formatting:

I believe there are some inconsistencies in how PO4E works with Asciidoc. Adding the additional line breaks should resolve the issues by explicitly setting the blocks.

.Procedure: Starting and Checking Proxy Status

. Start the proxy by calling:

+

----
mgrpxy start
----

. Check container status by calling:

+

----
mgrpxy status
----

+

Five {productname} Proxy containers should be present and should be part of the [literal]``proxy-pod`` container pod:

* proxy-salt-broker
* proxy-httpd
* proxy-tftpd
* proxy-squid
* proxy-ssh