-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support i18n #47
Comments
Current support is as follows: when you (`for`) `await` an LDflex path,
then you get back an RDF/JS term corresponding to the RDF/JS specification.
If the term is a literal, then it will have a `.language` property
indicating the locale.
What you can do now is loop over all the literals and filter those you need.
In the future, I’d want to add:
- a built-in filter mechanism so you can pick
- a preference for languages (based on the user profile) such that the
applicable one is filtered automatically
…--
This e-mail, and any attachments thereto, is intended only for use by the
addressee(s) named herein and may contain legally privileged, confidential
and/or proprietary information. If you are not the intended recipient of
this e-mail (or the person responsible for delivering this document to the
intended recipient), please do not disseminate, distribute, print or copy
this e-mail, or any attachment thereto. If you have received this e-mail in
error, please respond to the individual sending the message, and
permanently delete the email.
|
I would like to learn how to fix this issue. selecting: fruit.label.en I have been spending 4 hours on it. The LDFlex library seems complex.
Are these steps correct? |
If I understand it correctly it will be hard to detect what languages are possible. |
I have a proof of concept with one big pitfall. The languages are hardcoded. So it would not be possible to merge it. |
Just wondering if it might be interesting to use JSON-LD's |
Do you mean something like: |
Something more like this: Context:
LDflex expression:
|
Ah nice! that is great. So also:
|
Yep, JSON-LD defines that behaviour, so it would make sense if LDflex would inherit that. |
It is now also possible to set the default language via the context with:
However I am struggling with these proxies. |
Is internationalization currently supported?
If yes, how are we able to get language-specific data from a node?
The text was updated successfully, but these errors were encountered: