Per-page translations
See original GitHub issueWhat problem does this feature solve?
I have lots of documentation pages with non-repeating text blocks.
I’d like to be able to load the translations for these respective pages only when accessing them.
This would immediately improve a site’s loading speed.
What does the proposed changes look like?
The way I see this, a good solution would be to have the same file structure you have in pages, but inside of the lang
folder.
If you’d have pages/about.vue
, the corresponding translations would be lang/en/about.js
or lang/fr/about.js
.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:10
- Comments:22
Top Results From Across the Web
Translation costs per page
350-500 words on a page and if we translate one word for EUR 0.065, the translation price per page is somewhere between EUR...
Read more >Translation Per Page - Trusted Translations
Translation work can be charged in different ways. There are certain standards that are used and they can change depending on the text,...
Read more >Cheap Certified Translation Services - $20 per page
If you need cheap certified translation services with fast turnaround and guaranteed acceptance at USCIS, get it from us at $20 per page....
Read more >Per page Vs Per word rate - Translation Services - Frenchside
Per-page price is determined by an estimate number of words on a single page. Per page pricing can be quite expensive and can...
Read more >Translation Rates - Translation Cost - Translated
The translation of a standard page costs on average US $25, considering an average of 250 words per page, or 1,500 characters including...
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
I there any progress or way to do that?
Why not set lazy loading language for specific components in the same format as in nuxt.config.js ?
This would not only solve lazy loading but also different fallback per page, which I happen to have use case for … 😉