[Register add-on in translation system]: readonlyProfiles

[nvdaes]

Add-on name

readonlyProfiles

Add-on maintainer

@nvdaes

Stable branch

• Stable branch exists in add-on repo

[github-actions]

The pot files were built from the stable branch.

[seanbudd]

@nvdaes - can this be closed?

[nvdaes]

@seanbudd, yes, let's close this now.
BTW: seems that we can now register add-ons in Crowdin, and this is working well for Goldwave add-on, except minor issues since for any reason two languages are not handled well, and we have 63 instead of 65.
I wouldn't like to register add-ons in two different system, crowdin and mrconfig. According to a survey, most translators prefer to use Crowdin.
Unless other person contacts NV Access to register add-ons in mrconfig, I'm planning to switch to Crowdin, and then I can create a PR to add crowdin or replace info about mrconfig, if nobody would like to register add-ons in mrconfig.

[seanbudd]

@nvdaes - do you think we should archive this repository (public, read-only)?

[nvdaes]

You my archive this repo, and revoke my access to NV Access server.
Then perhaps SVN would work, but new add-ons would have to be registered by Crowdin.
But if you want wait until Octover or so, to create an NVDA add-on so that translators can upload and download files from Crowdin without using the web interface.
If the Crowdin API client is removed from NV Access, the add-on would need to include it.
Anyway, I don't know what will happen if the number of add-ons increases. I or Crowdin managers have to download the pot and xliff files to crowdin, and then add a title and the path, for example: goldwave/woldwave.xliff, and the same for .po. In this way, when translations are exported each add-on has its own folder for easy management.
And I don't know if with many add-ons it would be accessible for screen readers manager. I don't find a way to activate the notifications so that translators can be informed when new strings are available. I think that this is not accessible, and in this case I would require assistance from sighted people.
I can ask in my job or to other people, in some moments, but I cannot be sure if they will be available when I need it. So it's better to ensure the accessibility of the whole process.

[seanbudd]

@nvdaes - Are you no longer using the l10n server? I figured it was still used, if only for the legacy add-ons website and removing add-ons from the translation system.

I'm not sure I fully understand the issue you are describing with Crowdin. Is there a discussion/issue somewhere explaining the technical issues you are facing with Crowdin?

[nvdaes]

@seanbudd, in fact I'm using the server. My comment was to say you that, when all is imported to Crowdin, you may decide to revoke my access to the server.
I'm not reporting the issues facing with Crowdin since I'm not sure if this is something that I don't know how to achieve, for example getting notifications. And I don't know what will happen when a lot of files are added. I'm not experimenting a real issue with this, just that I don't know if it would be accessible, and this is my fear: that we shutdown the SVN system and then something is wrong with Crowdin accessibility.
About the 63 languages, and not 65, fetched when translations are exported, I don't know if this should be reported.
I think that I didn't have a good experience reporting an issue with Poedit accessibility. I tried to explain things, but seems that the developer and I didn't get a good communication, and @CyrilleB79 explained that we are blind, but I don't know if this was finally understood.
So I try to find out things myself before reporting issues to Crowdin. Also, I think that something answers are provided by IA, not humans, so I'm waiting a little to see if I can at least get notifications and the 65 languages.

[nvdaes]

FYI, I'm studying the crowdin api client included in NVDA, and I think that we may upload source files without using the web interface. I'll try to create an add-on not just for translators but also for managers. I have seen something about notifications in the API client too.
It's possible that I get stuck, and in this case I'll request for help to the community.