jcsteh / osara

OSARA: Open Source Accessibility for the REAPER Application
GNU General Public License v2.0
127 stars 46 forks source link

The Crowdin platform for translating OSARA is no longer accessible #986

Open reaperaccessible opened 7 months ago

reaperaccessible commented 7 months ago

The Crowdin platform is increasingly impossible to use. Personally, I stop using it because it takes too much time to just translate a few words. I can't even use the filter to display only what I want anymore. So I have to click on random buttons and hope I land on the right button. If it's the wrong button, I have to close the Chrome browser page and reopen it. The translation of OSARA requires a completely accessible and efficient service. For the Reaper translation, Justin coded us an in-house software that is completely accessible and super efficient. I'm in charge of the French translation of Reaper. I use his software and it works very well. But this one works with strings of 16 characters at the start of each line to be translated. So I highly doubt that we can use it with OSARA. But maybe I'm wrong and it's possible. Download link here : https://www.landoleet.org/i8n/LangPackEdit005_win64.zip Or does anyone have any ideas for another translation service that can be accessible online? Thanks guys.

jcsteh commented 7 months ago

I assume this is a fairly recent shift? There were always a few accessibility issues, but it seemed pretty reasonable when I was looking at this a couple of years ago.

I considered using the Cockos translation framework, but there are number of issues which make it very difficult to use for OSARA. Notably, you can't have separate language packs for each extension; it has to be a single language pack for the whole of REAPER. Also, you have to manually use the merge tool to merge with the template, which is a bit complex for less technically inclined translators.

Note that you can download the po file from Crowdin, translate it locally and then upload it if you wish. PoEdit also syncs with Crowdin.

I know NVDA is switching to Crowdin now, so we might hopefully be able to get some attention on any accessibility issues.

CC @MichaelDCurran for awareness.

jcsteh commented 7 months ago

I just visited: https://crowdin.com/editor/osara/4/en-frca?view=comfortable&filter=basic&value=0 which is the translation page for French, Canada. The search box still appears to be labelled, as does the field in which to enter your translation. The message to translate is just above that field. However, it's probably quicker to just stay in the translation field and use keyboard shortcuts like this:

  1. Control+shift+c to copy the source message into the translation (so you don't have to read the text above).
  2. Control+enter to save the current string and move to the next.
  3. Control+up and down arrows to move between messages.

Control+s will save the translation as a po file. Control+insert (you'll need to double tap if you're using NVDA) lets you upload a translated po file from your computer.

There are definitely a few unlabelled buttons which need to be fixed, but this doesn't look markedly worse than I remember.

reaperaccessible commented 7 months ago

Yes I know these keyboard shortcuts well. But the biggest problem is that it is now impossible to use the search filter. Impossible to display only untranslated strings. At the top of the page I can read that there are 10 untranslated words. I didn't even know there were untranslated words. I can no longer display only untranslated strings. Yes I can download the .po file and translate it manually, but it would take to much time. I'm going to request an accessibility improvement but ...

jcsteh commented 7 months ago

I mentioned the option of downloading because that's effectively what you do with the Cockos system. If you downloaded it, you could find untranslated strings by searching for theis string in a text editor: msgstr ""

Obviously, that's not a satisfactory situation, but I'm suggesting it as a possible interim solution.

jcsteh commented 7 months ago

Two other things:

  1. The filter button is the one just before the search field. So you can get to it quickly and reliably by going to the top of the document, pressing e, then pressing shift+b.
  2. This URL will consistently get you to fr_CA with the untranslated strings filter enabled: https://crowdin.com/editor/osara/4/en-frca?view=comfortable&filter=basic&value=2