There was some discussion today regarding translations of Dataverse. The Weblate idea seams dead and there are not many great OSS projects for translation management around. Should we ask https://lilt.com/academic for support?
I also found 1 (!) other tool that explicitly supports OSS projects: https://tolgee.io/pricing
Yes. Yesterday during the frontend meeting I mentioned that there is a need to support right to left languages down to the level of button placement.
I think that grant proposal has been submitted!
@Don Sizemore are there enough buttons below that we can go ahead and create that issue?
Screenshot-2023-03-21-at-14-11-49-Dataverse.png
all you need is one.
@Don Sizemore can you please ask your guy to give us the strings? Just in an email or whatever. I'm not asking or anyone to touch the git repo.
I did, but he's at RDA this week.
Ah. No rush.
I agree to create the issue!
@Philip Durbin As for what you mention about whether there are enough buttons to start the right to left support, I have a few concerns:
When does the proposal stakeholders expect the right to left functionality to be ready? (I mean, released for production use) We are still in the initial phase of developing the MVP of the SPA.
It may be a good time to consider right to left support in the SPA, since we are now defining the initial UI components and their behavior, but this would affect the scope of the MVP, which is to replicate part of the existing functionality, not add new one (Sticking to the initial planning, this would be a Post-MVP project).
We need to understand how the right to left support fits into the SPA development timeline. We can talk about this at the weekly frontend meeting tomorrow. I would like to know what Stefano thinks about this.
On the other hand (And this is more for the future), while changing the button orientation seems simple, I would ask for some mockups or wireframes before development.
Yes, let's absolutely discuss more. My thought was to create the issue after we can create screenshots showing our "hello Dataverse" page with the buttons mirrored and in a right to left language. The screenshots would make the situation much more clear (than no screenshots) and would be a visual we could keep in our minds as we design the components.
I think we're in violent agreement. :happy: I'm just thinking some screenshots in an issue that would be addressed post-MVP would be nice.
All I really want in an issue is a couple screenshots to make it super clear what we're talking about in terms of button placement etc. I'd say we could use these from Facebook, rather than creating our own Dataverse-specific screenshots:
Screen-Shot-2023-03-22-at-4.23.14-PM.png
They're from https://www.smashingmagazine.com/2017/11/right-to-left-mobile-design/
I meant to share this one a while ago: "The Turing Way" uses https://crowdin.com to manage translations. They do have a free plan for public projects...
@Slava Tykhonov @Philip Durbin I had a someone from the #community-i18n-de reach out to me - they did a translation for 5.13 to de_DE and want to share this with upstream. What are the latest things to point people to for l10n of DV?
Hmm, maybe recently merged PRs: https://github.com/GlobalDataverseCommunityConsortium/dataverse-language-packs/pulls?q=is%3Apr+is%3Amerged
@Don Sizemore you wrote https://groups.google.com/g/dataverse-community/c/yskq1C-nxJs/m/WXbz2fG2AQAJ a while ago... Any progress since then?
Oh, you're more asking about the status of Weblate, I guess.
I'm completely uninvolved in the l10n activity, so I have no idea what's actually going on
I mean, pull requests are being merged. To me that's important.
But more and better tools would probably be helpful.
I'd suggest reading https://guides.dataverse.org/en/6.0/installation/config.html#internationalization
https://preview.guides.gdcc.io/en/develop/installation/config.html#tools-for-translators includes a video
Oliver Bertuch said:
Don Sizemore you wrote https://groups.google.com/g/dataverse-community/c/yskq1C-nxJs/m/WXbz2fG2AQAJ a while ago... Any progress since then?
We last left off in Braga. Weblate will host open source translation projects for free, provided that the associated GitHub repo live in the same org as the parent OSS project. Jim and Gustavo wanted the translations to continue to live in the community repo, however, so Gustavo was going to contact Weblate to ask if they'd still host us for free. Gustavo was going to do this because he's the lead software architect and has a Harvard e-mail address.
@Don Sizemore I see. Would it make sense to take a look at alternative tools? (Like Crowdin)
Oliver Bertuch said:
Don Sizemore I see. Would it make sense to take a look at alternative tools? (Like Crowdin)
Sounds fine by me, though at a glance I didn't find the terms of their "generous open source plan"
Not especially generous, no
I'm happy to send an email from my Harvard address if it helps.
We probably don't need more than 1 source branch...
Also:
Yes. If you want to use Crowdin for an Open Source project, sign up for a free account, set up your project and send us a request. Apply for an Academic License if your project has educational purposes. Each granted license will include an unlimited number of projects, strings, and members.
https://crowdin.com/page/open-source-project-setup-request https://crowdin.com/page/academic-license-project-setup-request
Before submitting this form, please ensure that your project meets the following criteria:
You have created a translation project in Crowdin.
The project is licensed under an approved license from an open-source initiative.
Your project's source code is publicly available for download.
You do not have any commercial products related to the open-source project you are requesting a license for.
You are the project lead.
You have been working on your open-source project for at least three months.
You have an active community of collaborators.
You keep the "News" section of your website up to date.
You release updated builds on a regular basis.
So no restrictions with regards to where sources are located I suppose
Maybe this is the reason why such a large project as Turing Way is using their service... They probably have a lot more than 60.000 words :-D
https://www.youtube.com/watch?v=WiIxney3ORU is the video I was thinking of
What about translating the new React frontend? Does it matter what tool we use?
There's also https://groups.google.com/g/dataverse-internationalization-wg
Philip Durbin said:
What about translating the new React frontend? Does it matter what tool we use?
The last I heard, the JSON structures weren't ready yet? (if they are, I'm interested)
Let's see some Arabic.
I just created a doc called Internationalization (i18n) in Dataverse. Feedback is welcome! My goal has been to try to understand the various ways we support i18n in Dataverse across various features and subsystems. There's quite a variety!
@Oliver Bertuch @Don Sizemore @Eryk Kulikowski the plan is to talk about this doc and i18n in general, including for the SPA, at next week's tech hours (Oct 21)
I just posted about it here: https://groups.google.com/g/dataverse-internationalization-wg/c/x_YSgznx3E8/m/cXUy1MhSAAAJ
@Slava Tykhonov I bet you'd be interested as well.
@Amber Leahey or @Bikram maybe you can let Jayanthy know.
We took some notes if anyone is interested! https://docs.google.com/document/d/19XH9PUSRDIsF0_OkB0kJ1g7HEJTGmxdJOfCXadlN-CI/edit?usp=sharing
Last updated: Nov 01 2025 at 14:11 UTC