Rebuild front-end translation system #1024

Closed
opened 2026-02-04 23:26:38 +03:00 by OVERLORD · 3 comments
Owner

Originally created by @ssddanbrown on GitHub (Feb 4, 2019).

Originally assigned to: @ssddanbrown on GitHub.

Just putting this as a reminder to myself really.

Need to cleanup front-end translation system (/translations endpoint).
It's a badly-done system, inefficient system.

Instead only the translations used should land in the browser. Insert those via standard tags then parse out with standard JS. Translations could be defined near where but have blade stacks gather these into a common location.

Originally created by @ssddanbrown on GitHub (Feb 4, 2019). Originally assigned to: @ssddanbrown on GitHub. Just putting this as a reminder to myself really. Need to cleanup front-end translation system (`/translations` endpoint). It's a badly-done system, inefficient system. Instead only the translations used should land in the browser. Insert those via standard tags then parse out with standard JS. Translations could be defined near where but have [blade stacks](https://laravel.com/docs/5.5/blade#stacks) gather these into a common location.
OVERLORD added the 🔧 Maintenance🏭 Back-End💻 Front-End labels 2026-02-04 23:26:38 +03:00
Author
Owner

@ezzra commented on GitHub (Feb 5, 2019):

Instead only the translations used should land in the browser.

I dont understand that very well, isn't that the case already? The textes are translated in backend when the html file is generated, arent they?

@ezzra commented on GitHub (Feb 5, 2019): > Instead only the translations used should land in the browser. I dont understand that very well, isn't that the case already? The textes are translated in backend when the html file is generated, arent they?
Author
Owner

@ssddanbrown commented on GitHub (Feb 6, 2019):

@ezzra Yeah, This is more for translation used inside of JavaScript components which is handled on the front-end, differently to the majority of the translations which are inserted within the back-end blade files.

@ssddanbrown commented on GitHub (Feb 6, 2019): @ezzra Yeah, This is more for translation used inside of JavaScript components which is handled on the front-end, differently to the majority of the translations which are inserted within the back-end blade files.
Author
Owner

@ezzra commented on GitHub (Feb 6, 2019):

Ah ok, I totally missed the front-end and was confused :)

@ezzra commented on GitHub (Feb 6, 2019): Ah ok, I totally missed the _front-end_ and was confused :)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#1024