-
Notifications
You must be signed in to change notification settings - Fork 491
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
Internationalization : redesign the architecture to handle metadatablocks #4684
Comments
@JayanthyChengan It may make sense to have internationalization handled separately, but I'd be curious to have your input on how it might fit into something like #4451. |
Hi @4tikhonov : Thanks. Will do PR soon after committing french metadata files. |
Hi @JayanthyChengan, thanks, I see, it's good idea to have a separate folder for translated properties. I'm looking forward to see it in the master branch, we'll use it for DataverseEU as well. |
@JayanthyChengan, we've introduced ISO codes in DataverseEU for all languages we're supporting, can you please also test this properties with current release? Also we modified |
@JayanthyChengan thoughts on removing columns from db? It's not ideal to have duplicate info. (alternatively, the code could expect to use the db if the primary language and only use the bundle otherwis; but that seems like possible overkill in logic) |
@scolapasta, the ideal solution for DataverseEU is to use controlled vocabularies as properties delivered as microservice with language parameter. We're connecting Dataverse to ELLST multilingual thesaurus now (13 languages, distributed as RDF) to get similar functionality. |
@scolapasta - PR #5290 is the latest one with all changes. |
@JayanthyChengan thanks for all work on this! Shouldn't your pull request include a change to the rst file for http://guides.dataverse.org/en/4.9.4/admin/metadatacustomization.html to explain to creators of custom metadata blocks that they must create not only a TSV file but also a bundle file? Once your pull request is merged, I mean. |
@pdurbin @scolapasta , updated doc/sphinx-guides/source/admin/metadatacustomization.rst in the PR #5290 , please review it. |
@JayanthyChengan I didn't |
@kcondon please let me know, if I can answer any of your questions. Thanks |
@JayanthyChengan Thanks, I have been occupied with other issues but hope to get to this shortly. |
@JayanthyChengan This looks good and hope to merge shortly but ran into a slight doc issue with unicode char when building pdf format. I'm checking with the team to see whether this is something we need to worry about. For what it's worth, here is the doc build error for pdf. html works fine: ! Package inputenc Error: Unicode char ṭ (U+1E6D) See the inputenc package documentation for explanation. l.3758 ...age.marathi_(marathi)=Marathi (Marāṭ l.3758 ...age.marathi_(marathi)=Marathi (Marāṭ |
@JayanthyChengan Yes, that did it. Thanks! Merged. |
Have to figure out, how internationalization will be handled for the files under scripts/api/data/metadatablocks, so that new dynamic content, like domain metadata fields, can be added to the application and available in all languages.
The text was updated successfully, but these errors were encountered: