>>I suppose this is where the notes should be scanned (by a human rather >>than a script) to see if they can improve the documentation. > > Well notes are checked anyway - quite a few are rejected or deleted > before they ever appear on the site. I > >>Moving the notes away from the page may not be a great idea. If the >>notes where tagged with the language they are in (based upon which >>manual was used to add the note maybe) then have these sorted first, so >>you see notes in your language and then other languages - maybe. > > I think tagging them with the language they're in would be a good > thing to do. That way the new note notification can be directed to the > relevant translation team and reviewed by them. Perhaps on the manual > pages, it would show all the notes for that language, and on the > non-English pages, there could be an option to show notes that are in > English. Or just show all notes on the non-English pages regardless.
Do not dream about such options, we need cacheable pages. An URL should be uniquely matchable to a source code (HTML+CSS+JS) representation, without considering any other data. This lets us leverage caching (look into livedocs cache for example), and accurate search engine results. Goba