Add missing translation keys - #1764
Conversation
|
@justvanrossum I am wondering if we really want to have a unique translation for undo (always)? Here an example: Would be great to get you feedback and advice. Thanks a lot in advance. |
d2de642 to
40e5fef
Compare
|
As discussed yesterday, this translation key update is almost complete, but we decided to leave it as it is, so that we do not spend too much time on translations and can focus on other features. |
… be english always
bfda384 to
fc4534c
Compare
…pdate language files
…ment-status-definitions.undo.change
…nge is more generic now
Fixes #1763 and fixes #1752
This is the first part of the rework for missing translations.
I split it up, because it may get messy otherwise. This PR includes commits based on each file (Related Glyphs, Glyph Note, Shortcuts panel, Sources Panel and Status Definitions panel). But the next work might not be structured this nicely anymore, because the strings are all over the place.
So, I created another branch where I first marked the missing translations:
https://github.com/googlefonts/fontra/tree/issue-1752-missing-translation-keys-2