Does anyone know what happens, when we remove translation strings from 1.x that exist in 1.9?
Won't Transifex then drop them from its database, which results in a situation where translators are not able to translate those strings anymore for 1.9?
(I'm asking because this PR would remove the 'garbagecollector:<interval>' translations keys.)
info@elgg.org
Security issues should be reported to security@elgg.org!
©2014 the Elgg Foundation
Elgg is a registered trademark of Thematic Networks.
Cover image by Raül Utrera is used under Creative Commons license.
Icons by Flaticon and FontAwesome.
- Evan Winslow@ewinslow
Evan Winslow - 0 likes
- Paweł Sroka@srokap
Paweł Sroka - 0 likes
You must log in to post replies.Yes, all branches share the same strings so don't remove any. That's also technically backwards-incompatible so we shouldn't be deleting them in the 1.x series anyways. When we work on 2.0 we'll probably want to add a new Transifex project (unfortunately!). They just don't support branching very well.
FYI Transifex should have something functionally similar to tagging as well (releases AFAIR), but people complain about it as it's hard to change existing release.
No branching as far as I can tell.