You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 3, 2023. It is now read-only.
A request to localize the interface into German was requested. Dutch would be trivial as well. Other languages could be added later
In order to avoid duplication, we'd need some kind of template or build system for the HTML. We could even move to a frontend-system like e.g. yew or another for this.
But the simplest would be a search/replace template that builds index.html in english, de/index.html in German and nl/index.html in Dutch.
It would grab the strings from a yaml, po or json file and compile them into the final HTML.
If yes, localize it. As a german speaking user I don't feel addressed by the job search.
... Flockingbird @flockingbird
@flockingbird I'd expect a german user interface with a filter based on german cities/regions. With the filter applied only toots appear that advertise jobs in that region. For the language of the toots itself I have no preference. I'd recommend not to exclude english toots that contain job descriptions for jobs in german cities since this is pretty common.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
A request to localize the interface into German was requested. Dutch would be trivial as well. Other languages could be added later
In order to avoid duplication, we'd need some kind of template or build system for the HTML. We could even move to a frontend-system like e.g. yew or another for this.
But the simplest would be a search/replace template that builds index.html in english, de/index.html in German and nl/index.html in Dutch.
It would grab the strings from a yaml, po or json file and compile them into the final HTML.
The text was updated successfully, but these errors were encountered: