Add specification for Translation Memory Management
What the title says.
Should we consider a way to add a new entry without uploading a .tmx file?
Do we need a way to identify strings with the exact same text (and potentially same translation) - for example which project the string is associated with?
Do we need a way to identify strings with the exact same text (and potentially same translation) - for example which project the string is associated with?
To some extent, sorting the strings in alphabetic order should help with that. Anything beyond that I would keep for a follow-up, so I added it to the Out of scope section.
Should we consider a way to add a new entry without uploading a .tmx file?
IIRC the conversation from Dublin, we didn't find a good reason why somebody would want to do this? If the string is in Pontoon, why wouldn't you just add a translation for it and as such also a TM entry? If it's not in Pontoon, why do you need a TM entry? Uploading .TMX files is different, because a large set of TM entries has a match higher chance of affecting partial matches.
My preference would be to keep this out of scope, because there's a workaround (just create a .TMX file and upload it). If there's an actual demand from users, we can always add it later.
One thing that is missing is what happens when you edit or delete with entries that are grouped together:
- Delete: I assume we remove all of them
- Edit: edit all of them?
The latter brings up some doubts on how we store translation memories in the first place, but not sure if that's in scope for this or should be a separate conversation (it would definitely impact this).
One thing that is missing is what happens when you edit or delete with entries that are grouped together:
* Delete: I assume we remove all of them * Edit: edit all of them?
Made it clearer in the spec the actions apply to all entries.
I've made this change after the PR was approved, which I've previously mentioned in the comment. That way all 3 actions are logged, and we at least have some data to track changes for the Delete action.
Since it's a minor change, I'll go ahead and merge, but please let me know if you disagree with the change.