Skip to content
This repository has been archived by the owner on Oct 16, 2020. It is now read-only.

Duplicated Items - make able to disable it for single entries #387

Open
xstable opened this issue May 1, 2020 · 7 comments
Open

Duplicated Items - make able to disable it for single entries #387

xstable opened this issue May 1, 2020 · 7 comments

Comments

@xstable
Copy link

xstable commented May 1, 2020

Sometimes it's perfectly fine, if Entries are dublicated in two languages.
For example: The name of an App:

image

Would be great, if you could add a functionality to disable the "warning" manually for single entries.
This would give an better overview for entries which are e.g accidentally still not translated.

@gilmarsquinelato
Copy link
Owner

gilmarsquinelato commented May 1, 2020

But this would result in a temp file for just these things, creating trash in the disk.
Don't know if that feature would be widely used, because it would be for only a few numbers of keys.

@bmarotta
Copy link

bmarotta commented May 9, 2020

I vote for it. It is even worse. In some languages the translation is identical. I have too much "false" negatives in the project. The settings could be saved in a separate folder.

@gilmarsquinelato
Copy link
Owner

So for this feature, should we disable for the whole key, or for specific languages inside the keys?

@bmarotta
Copy link

For the first implementation I think it is enough to disable it for the whole key. If any of the translations for the key is changed, then the check is re-enabled and must explicitly disabled again.

@gilmarsquinelato
Copy link
Owner

I think that it could be a toggle in the context menu, that only enable/disable by clicking on it.
Maybe "ignore checks", that it will ignore missing and duplicated items.
If the user changed, he will eventually change both keys, making it not required to re-check.

@bmarotta
Copy link

In the case, you introduce a new language, resetting the ignores is needed.

@gilmarsquinelato
Copy link
Owner

So we should ignore the languages inside the keys, not the whole key.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants