What do folks think? I’m not in a position review any of this, being illiterate in this language. Do we want to enforce our traditional “must have a second fluent reader” requirement, or do we want to get these out there in the name of having more translations, and wait for reports from users if there’s a problem?
—Rich > On May 7, 2026, at 8:06 AM, Leonardo Lara Rodrigues > <[email protected]> wrote: > > Greetings! > > This is my first contribution to httpd docs. > My goal is to have all the manuals (2.4 and trunk) translated to pt-br > in the near future. > > Find attached some initial patches for httpd pt-br docs translation. > They also change the encoding to UTF-8. > > These are all for the 2.4.x branch only. > > docs/manual/howto/htaccess.xml.pt-br -> htaccess.xml.pt-br.patch > docs/manual/index.xml.pt-br -> index.xml.pt-br.patch > docs/manual/new_features_2_0.xml.pt-br -> new_features_2_0.xml.pt-br.patch > docs/manual/new_features_2_2.xml.pt-br -> new_features_2_2.xml.pt-br.patch > docs/manual/style/lang/pt-br.xml -> pt-br.xml.patch > docs/manual/style/lang-targets.xml -> lang-targets.xml.patch > docs/manual/style/manual.pt-br.xsl -> manual.pt-br.xsl.patch > docs/manual/style/xsl/util/designations.xml > designations.xml.patch > > Let me know if this is the best format for this kind of patch e-mail. > If not, please send me an example of best practices. > > Thanks, > Leonardo Lara. > <lang-targets.xml.patch><pt-br.xml.patch><new_features_2_2.xml.pt-br.patch><manual.pt-br.xsl.patch><new_features_2_0.xml.pt-br.patch><index.xml.pt-br.patch><designations.xml.patch><htaccess.xml.pt-br.patch> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] — Rich Bowen [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
