Description of problem: pt_BR documentation related to Red Hat Enterprise Linux types of services is broken. The auto translation tool should not be translating reserved words(commands, file names) and that is more explicitly shown at Squid chapter, making it look low quality for the Customer: Chapter 7 - Configuring Squid - https://access.redhat.com/documentation/pt-br/red_hat_enterprise_linux/8/html/deploying_different_types_of_servers/configuring-the-squid-caching-proxy-server_deploying-different-types-of-servers#masthead # yum instalar lula -> this is a literal translation to yum install squid acl Porta SSL_port 443 -> Port should not be translated to Porta, incurring on syntax issues on that tool # systemctl habilita --agora lula -> should be "systemctl enable --now squid". Even command verbs/arguments/phrases are being translated This is NOT RESTRICTED to the Squid chapter, but it was the one I've noticed first, and where errors are more "eye catching". If you look at the Apache documentation, there are minor errors, but they still exists: https://access.redhat.com/documentation/pt-br/red_hat_enterprise_linux/8/html/deploying_different_types_of_servers/setting-up-a-single-instance-apache-http-server_setting-apache-http-server # yum instalar httpd -> install should not be translated. I suggest reviewing all the translation process, or at least, the translation process of those reserved blocks that shouldn't be translated at all. How reproducible: - Access Red Hat official documentation, pt_BR language, types of services chapter. Steps to Reproduce: 1. Access: https://access.redhat.com/documentation/pt-br/red_hat_enterprise_linux/8/html/deploying_different_types_of_servers/configuring-the-squid-caching-proxy-server_deploying-different-types-of-servers#masthead Actual results: Commands, filenames and command outputs are being translated, making the documentation look amateur. Expected results: Commands, filenames and command outputs should not be translated.
This is just to confirm that the localization team got your request and we are working on it.
After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.