| 4 | | Three reasons to keep it there: |
| 5 | | 1. The table with the Language specific notes and suggestions in its current – and mostly empty – state can not be final, sure. [[br]] [[br]] But as the [wiki:/Translations#Languagespecificnotes Dutch] example shows, the translator took the foreign English terms as suggestion to fill the gaps with the native ones. I think that the table in other languages will see a similar development. |
| | 4 | ~~Three reasons to keep it there:~~ |
| | 5 | ~~1. The table with the Language specific notes and suggestions in its current – and mostly empty – state can not be final, sure. [[br]] [[br]] But as the [wiki:/Translations#Languagespecificnotes Dutch] example shows, the translator took the foreign English terms as suggestion to fill the gaps with the native ones. I think that the table in other languages will see a similar development.~~ |
| | 6 | ~~1. This table can be a target for guiding links from external systems. See this suggestion in https://help.launchpad.net/Translations/Guidelines. Perhaps we have such a static guidance already and I did not find it.~~ |
| | 7 | ~~1. It is a place to communicate. Currently I see no structured ways or means for the translators interested in one language to communicate with each other. We need a Meta Translation Bug for each language. A mailing list for JOSM translations would lack all benefits Trac has. [[br]] [[br]] And tables like this support communication, only by the limited means of a wiki, but they do. (The English variant can solve the question if JOSM deals with ''elements'' or ''objects'' and what the difference between them is.) To give each translation a start the English page needs a prefilled hull. ~~ |
