Plurals for some Spanish translation strings

[ElCrackLoko]

Hi James, Scot, and all the other guys on the OSARA team.
I would like to request more control for the "none" translation strings, as that string is used for both tracks and MIDI channels. In Spanish, "track" is feminine and "MIDI channels" (in the send parameters of the OSARA parameters window) are masculine.
Also, regarding the term "Frozen" with a capital F used when OSARA reports how many frozen tracks there are, it says something like: "Frozen: 1 vocal" if we have a frozen "vocal" track. But if we have nothing frozen, it says "Frozen: none". The "none" string doesn't fit there because it's masculine by default as I mentioned above, but in the case of tracks, it should be feminine.
I would also need plurals for that line. If I have 2 frozen tracks, I could adapt it so OSARA says "in frozen state" (en estado de congelamiento), because if there's more than one frozen track, it lists them with their respective names.
The main problem is in the frozen track report when moving with the up and down arrows. In English, the order is: track number, state (frozen or not), and track name. But in Spanish, the correct way is: track number, track name, and then the state (congelada or no congelada).
I hope this isn't too much to ask; it's all to improve the translation.
A hug.

[jcsteh]

Thanks for your efforts in translating OSARA and for taking the time to report this.

First, I think it's important to understand that even in English, OSARA (and most screen reader access) often isn't grammatically correct, nor is it intended to be. Using true grammatically correct language would make the messages a lot longer. Also, it would make it very difficult to communicate lots of small pieces of information and would make determining that information much less efficient. For example, say you have a track called piano which is armed and muted. OSARA reports:

"1 armed muted piano"

If we were being grammatically correct, we'd actually want to write something like:

"Track 1 is titled piano and is both muted and armed."

That's slightly exaggerated, but hopefully, it illustrates the point. We don't report the state first for any linguistic reason. On the contrary, we report it first because it makes it faster to quickly skim through tracks and determine how the project is configured, just as sighted users can very quickly see the states of a track due to its icons. Customising the order is a valid feature request - different users have different preferences - but this isn't language specific and it's also very difficult to implement.

For the "none" message, it's possible to have different contexts for MIDI channels and the various track state queries; e.g. OSARA: Report muted tracks, OSARA: Report frozen tracks, etc. However, it's not feasible at this stage to have different versions of "none" for OSARA: Report muted tracks, OSARA: Report frozen tracks, etc. That is, all those commands would use the same "none", even though MIDI channels would use a different "none". Does that help, even if it only partially solves the problem?

[ElCrackLoko]

Hi James.
On the contrary, thank you for taking the time to read this. No problem, anything you can do would be helpful.
Hugs.