Hiding untranslated keys
See original GitHub issueI’m submitting a … (check one with “x”)
[ ] bug report => check the FAQ and search github for a similar issue or PR before submitting
[ ] support request => check the FAQ and search github for a similar issue before submitting
[x] feature request
Current behavior My keys are visible for a brief period before translations are loaded. This has an ugly effect on the loading of my website.
Expected/desired behavior An attribute could be used to show translated elements. My css could for example look like this:
[translate]:not([translated]) { display: none; }
Then when the translated attribute is added the translated text will become visible.
What is the motivation / use case for changing the behavior? To make it simple to hide keys until translation is complete.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:16
- Comments:5
Top Results From Across the Web
Option to hide items to untranslated Entities [#2895269] - Drupal
Entity based process trims unpublished translation links (from anom). Leaves items for those with edit/view access). Removes lid based links if ...
Read more >How to catch not translated keys when using @ ngx-translate
OK, here it is. Use MissingTranslationHandler as stated in comments. @Injectable() export class MyMissingTranslationHandler implements ...
Read more >qTranslate: Hide untranslated content
I create a very simple plugin which enables hiding menu items in some languages, but show them on others.
Read more >Key editor and key actions | Lokalise Docs
Learn how to manage your translation keys in the editor, link keys to platforms and ... Hide from contributors: hide the target key...
Read more >Common Questions | Crowdin Documentation
You can also make strings invisible from the Editor, Translation mode. In the top middle area open the menu and click Hide string....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
is there any update on this? Is this expected behaviour that will not be changed or is it something that is under consideration?
May be there is an option to hold the loading stage on the screen until translations are loaded? I mean that when the application starts and not functioning yet, the browser shows the contents of the app root tags, so maybe we can use some hooks to load the translations at this stage, so when the app starts rendering the page and replaces the
innerHtml
it would have the translations and won’t show the keys… Is there any way of doing it?