About [[Osm:Issues.show.reports/pt]]

This string is not being published, although it's correct.

This is a bug of the local message parser that does not handle that syntax for "PLURAL" (not "PLURAL") correctly, it does not accept the "zero=" parameter, and incorectly manages optional values (doesn't accept them if one clause returns an empty string), doesn't accept other clauses needed for other languages (notably in Asia), and just assumes that there can be two clauses, "one=" and the default value in last position, both having non-empty values (at least one space). The bug is reported multiple times in this support page (it is the fault of TWN; not OSM)

All messages in the OSM project using the proposed "PLURAL" exposed in the English source have this problem in all target languages of translations.

But its correction awaits some changes pending since long and needed on OSM (to support other languages that need more than 2 grammatical plural forms and an optional zero, but also without assuming that the default for zero is a plural, and offering a solution when the plural forms depends on sveral distinct values because it a single value is passed implicitly).

For now the best you can do is to submit the syntax that should work, even if it remains "fuzzy", and then contact the OSM support to propose a syntax that it will test; they will then update the translation here themselves to make it disappear, or a local admin will submit your proposal, using their admin tools; for now leave it fuzzy and let admins see if this can work when they test it without the fuzzy tag. It will be validated externally OSM developers and TWN admins have to decide what to do for the supprot of plural forms in their apps or within their export/import tools if they need to convert these messages into a syntax that the OSM website can process correctly. Until some development is made by OSM, everything such issues will have to handled manually by them (just recall them that there are new pending "FUZZY" messages to handle (once again for all messages that were recently modified in the sources and can't be updated correctly due to this longstandanding bug whose resolution is always postponed; this does not block them to update their website in English but makes its localization to other languages problematic as their support by the small core OSM technical team managing their website is still considered "non-urgent", even if it exists since many years, or they are not trained enough to work seriously on l10n issues and have still not granted access to other trained developers to test that essential part of their international websites and core applications.

Thank you for the explanation.