Closed denismaier closed 9 months ago
No objections; I'd assume this was an oversight
Ok, I'll add it. Just a question: Do we have a way to add to it all locales where the term is missing? IIRC, @zepinglee had something like this.
I've just done it manually in the past
Previously I wrote a script to resolve duplicate terms in all locale files (#269). It was relatively easy so I split each locales-*.xml
file into lines and made some modifications. However adding missing terms is not trivial and special care must be taken. First, some terms are missing because they are identical to their default "long" forms. For example, in locales-nn-NO.xml
the <term name="no-place" form="short">
is missing and we cannot copy the one from locales-en-US.xml
.
Secondly, in some edge cases the position of copied terms is not as expected. This is similar to git merge
which may have conflicts.
I've written a script https://gist.github.com/zepinglee/e6d0076a89b0266c9c9886fd83aacd99 and it should work in most cases.
I open up VS Code, select the line before the one I want to add, then use find-and-replace to replace that line with two lines (the existing one and the new one). I then click on each file in the left sidebard and click the replace all button for each. Takes about 4 minutes to update all the locales.
I noticed that "number" is also missing. We should double check that all of the number variables are correctly listed.
I don't remember if that was on purpose or an oversight, but looks like the term for
collection-number
is missing. Any objections if I add it?@adam3smith @bwiernik