Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Traducción español #497

Closed
joseonce opened this issue Mar 22, 2021 · 39 comments
Closed

Traducción español #497

joseonce opened this issue Mar 22, 2021 · 39 comments

Comments

@joseonce
Copy link

No description provided.

@ScottChesworth
Copy link
Collaborator

Hi @joseonce, the you've opened is blank at the moment. Are you having a problem with Spanish translation? If so, tell us the details in a comment. Thanks.

@joseonce
Copy link
Author

joseonce commented Mar 22, 2021 via email

@jcsteh
Copy link
Owner

jcsteh commented Mar 23, 2021

Translations are managed on Crowdin. With Crowdin, you can translate entirely online on the web, upload and download translations as .po files or directly sync your translations using Poedit.

If you'd like to translate OSARA, you will first need to sign up for a Crowdin account. Then, please comment on this GitHub issue and include these details:

  • Your Crowdin username;
  • The language you'd like to translate to; and
  • The file name of the REAPER language pack (or packs) for your language.

Thanks for your work in translating OSARA.

@jcsteh jcsteh mentioned this issue Mar 23, 2021
Closed
@joseonce
Copy link
Author

joseonce commented Mar 25, 2021 via email

@jcsteh
Copy link
Owner

jcsteh commented Mar 25, 2021 via email

@jcsteh
Copy link
Owner

jcsteh commented Mar 25, 2021 •
edited
Loading

@Carlos-EstebanM, @joseonce, it seems there are multiple Spanish translators and I'm not clear as to whether you're collaborating or not? See #499.

@Carlos-EstebanM
Copy link

Hello.
No, joseonce not is a contributor in the translation from the team Produccion Musical Accesible.
The contributors are @ElCrackLoko with two people (don't have gitHub), Iván Zamonaro and David Blanco, and me.
Regards.

@jcsteh
Copy link
Owner

jcsteh commented Mar 26, 2021

Okay. @joseonce actually made the request to translate to Spanish first, so please coordinate with them. Thanks.

@Carlos-EstebanM
Copy link

Carlos-EstebanM commented Mar 26, 2021 via email

@ElCrackLoko
Copy link

Hello everyone. As my admin colleague said, we've been testing and working on the translation since February, and our goal was to upload it when it was complete, and that's almost done. I understand that @joseonce wants to translate now, but I don't know, in the PMA project we have been 4 people in charge of the translation, and since yesterday we have our collective crowdin account ready, but since the work is done as a team, no The request was sent until today that everyone gave their approval. I am a writer with a long history, so I have a good knowledge of Spanish.

@jcsteh
Copy link
Owner

jcsteh commented Mar 26, 2021 via email

@ElCrackLoko
Copy link

Ready, we already have 100% of the translation completed. We are only doing the last tests, and if you give us your approval, we can upload it and everyone is happy. Our crowdin user is produccionmusicalaccesible
As is well. It seems to me that my colleague @Carlos-EstebanM sent the request at 7 A.M. from Australia, I don't know if that was before the gentleman @joseonce

@jcsteh
Copy link
Owner

jcsteh commented Mar 26, 2021 via email

@ElCrackLoko
Copy link

Dear @jcsteh the translation of the PMA team has been completed, therefore it is already uploaded in Crowdin. Thanks a lot.

@joseonce
Copy link
Author

joseonce commented Mar 26, 2021 via email

@ScottChesworth
Copy link
Collaborator

Hey @joseonce, can you summarize your key map modifications for non-Spanish speakers like me? I wasn't anticipating each translation also bundling customized key maps, and I'm a little concerned whether I'll be able to provide support for that in the community channels that I moderate here.

@joseonce
Copy link
Author

joseonce commented Mar 26, 2021 via email

@ScottChesworth
Copy link
Collaborator

Aha, now I understand! Thanks. :)

@ElCrackLoko
Copy link

Hello Bro @joseonce. I liked the Curriculum that you put, that in your community there are 170 people and that you have a Blog and a YouTube channel. Congratulations. Just one thing, unlike you, we have not gone through a translator and I think that the correct translation for Muted is Muteado, but not Silenciado, since in Silenciado English it is Silent, just like Unmuted, which in Spanish is Desmuteado, more no not silenced like you put it. Of course, the BVBA indicates that the most appropriate verb is to silence, but in the Spanish production who says, wait, I'm going to silence the track. There are terms in the production that must be adapted in a way that the final essence is not lost. I believe that James will choose what he thinks is right, and those of Team PMA will respect the decision that is made. I do not recommend translating with a translator, since for example, if I translate with it, many things do not agree despite the fact that technology has advanced so much. Now, I'll just say one thing. If you have been translating for 4 months, why weren't you interested in translating Osara back then? I will not repeat what I said, but with Team PMA we have been doing tests since February so that everything is perfect.

@joseonce
Copy link
Author

joseonce commented Mar 26, 2021 via email

@ElCrackLoko
Copy link

Hello again Bro. Without so much preface I have to tell you that my conclusions are simple. No offense but, you have errors in some parts, verbs for example, you define feminine when it should be masculine, eliminated, for example, redundant errors, I don't like to criticize anyone's work, but. You wanted an answer, there I leave it to you along with some advice. Can you imagine if the translations were literal? And even though I am a writer, everything would be very strange. I hope we can have a coffee. Greetings from Ecuador.

@jcsteh
Copy link
Owner

jcsteh commented Mar 26, 2021

I am not going to arbitrate or make a decision here. I don't speak Spanish, so I am not able to make that assessment. You either need to sort this out civilly or I will remove the Spanish translation altogether.

@Carlos-EstebanM
Copy link

Carlos-EstebanM commented Mar 26, 2021 •
edited
Loading

***Sorry if you wach my coment two times (three emails with my name with this), an error of me using gmail because I sent a blank reply. I delete, This is my comment again:
Hi all.
OK, is possible submit and compile with the translation from PMA. Is complete, and Jose can read for learn and make comments about our translation. Also, Jose can be a contributor. So, the translation is from PMA and Jose Once.
Regards.

@ElCrackLoko
Copy link

Hello again. I agree with what my colleague @Carlos-EstebanM proposes
We use the PMA translation, and @joseonce can contribute whatever he thinks is right. But if the gentleman still does not agree, we could create 2 translations, yes, you would have to change the name of the .ReaperLangPack file manually, in the AppData/Reaper/LangPack folder.
Es-Es (Spanish from Spain) for @joseonce and Es-La (Spanish Latin American) for the PMA team, and that users use the one according to their needs and tastes. I think this is the most civilized way of doing things for everyone. Remember that this is not about who does more or knows more, but who does something to help others. And the others are from the PMA or RAE community.

@ElCrackLoko
Copy link

Based on the classic translation terminologies, the names would be something like this, the first 2 letters in lowercase, the _ sign (Underline) and the rest in uppercase, example: es_LA.po or es-ES.po
Greetings.

@joseonce
Copy link
Author

joseonce commented Mar 27, 2021 via email

@joseonce
Copy link
Author

joseonce commented Mar 27, 2021 via email

@ScottChesworth
Copy link
Collaborator

Es-Es (Spanish from Spain) for @joseonce and Es-La (Spanish Latin American) for the PMA team, and that users use the one according to their needs and tastes.

Given that there are differences between those dialects, that @ElCrackLoko has proposed a clear labeling system above, and also that translation files have to be placed manually right now anyway so this wouldn't be placing any additional technical hurdles in front of Spanish-speaking users, this seems like a reasonable way forward to me. Collaboration would obviously be the preferred solution, but that doesn't seem likely to happen here for some reason.
@jcsteh, if there can only be one translation per language, would you like me to round up a handful of Spanish-speaking users who I trust to be unbiased? Neither of us speak Spanish, so that seems like the least biased way to choose which translation OSARA will adopt. Gotta say, I'm not pleased about taking on extra admin because users can't resolve things without intervention, but if that's what it'll take to get OSARA into the hands of more users, I'll collate feedback and report back.

@joseonce
Copy link
Author

joseonce commented Mar 27, 2021 via email

@ScottChesworth
Copy link
Collaborator

ScottChesworth commented Mar 27, 2021 •
edited
Loading

The translation I have uploaded two hours ago is complete and revised.

I appreciate that you've worked hard on it man, but that comment doesn't move us forward out of this stalemate, where both parties are insisting that their work is the best option. As people who don't speak Spanish, neither @jcsteh or I can make an informed decision on this. It really does either need to be agreed between you, or become a decision that's handled by other Spanish-speaking users if you can't reach an agreement that is acceptable to all parties that have invested time and effort.

@jcsteh
Copy link
Owner

jcsteh commented Mar 27, 2021

Actually, translations do not have to be placed manually. They are bundled with OSARA itself. The idea is that specific REAPER langpack names map to specific OSARA translations. That's obviously going to be a problem here unless there are also two separate REAPER langpacks, one for each variant.

@Carlos-EstebanM
Copy link

Carlos-EstebanM commented Mar 27, 2021 via email •
edited
Loading

@jcsteh
Copy link
Owner

jcsteh commented Mar 27, 2021

As long as you're all aware that things will be harder for Spanish users than any other translation (since users will have to rename the REAPER langpack), I guess that's up to you. You will of course be responsible for providing instructions or support to users to manage this.

@ElCrackLoko
Copy link

Hello brothers.
The solution is already on the table, you don't have to complicate your life any more. Let each one use the translation that suits her needs with the Spanish that suits her best. Even Windows 10 itself has 2 languages. Spanish Spain and Spanish Mexico representing Latin America. Now, if it is decisive to take a single translation, I think the most fair thing is to take the one that was uploaded first, and that is the one from the PMA team that has not been revised again, because that was already done in the time it was mentioned. While, @joseonce has uploaded his translation, corrected. So, already speculating a little, what the gentleman did was upload as he had the work so that his translation is approved, correcting it later and uploading now, yes, the final translation. So I think he took longer.
But if we still want to be fair and upload the translation of the Hissue that was opened first, because I have several, the one from @Carlos-EstebanM on February 7, asking about translating Osara into Spanish,
#474 (comment)
And then on this one, on February 16, where we discussed and started testing since then.
#13 (comment)
We did not send Crowdin's request then because we were concentrating on the translation, on seeing what was the most appropriate.
In the following Link, he left the publication that helped us to do the tests with Osara, written by the esteemed @jcsteh
#477 (comment)
So, my solution is not to leave the colleague @joseonce out of this because I consider that everyone's time is valuable, but, he even proposed to collaborate with us who were the first volunteer translators as you can see, but he does not want to. There are solutions everywhere, you just have to take them.

@ElCrackLoko
Copy link

As long as you're all aware that things will be harder for Spanish users than any other translation (since users will have to rename the REAPER langpack), I guess that's up to you. You will of course be responsible for providing instructions or support to users to manage this.

If it is for the benefit of all, of course, those of the PMA team, at least we commit ourselves to our members to provide them in our folders, the new name of the LangPack so that Osara works in the correct language. They just have to enter the new LangPack file, they don't have to change anything else unless they want to do it themselves.

@jcsteh
Copy link
Owner

jcsteh commented Mar 31, 2021

I've created a Spanish Mexico translation and moved the PMA team account there. I can't create Spanish Latin America, unfortunately; standard locales have a list of countries, not regions. The locale code is es_MX.

So, I guess everyone is as happy as they're going to get and I'm going to close this. This has all been deeply unpleasant.

@jcsteh jcsteh closed this as completed Mar 31, 2021
@jcsteh
Copy link
Owner

jcsteh commented Mar 31, 2021

here's the link for managing the Spanish Mexico translation.

@jcsteh jcsteh mentioned this issue Mar 31, 2021
Closed
@joseonce
Copy link
Author

joseonce commented Mar 31, 2021 via email

@jcsteh
Copy link
Owner

jcsteh commented Mar 31, 2021

The sameway you uploaded the last one: go to the page for osara.po on Crowdin, press control+insert (twice if running NVDA).

@jcsteh jcsteh mentioned this issue May 8, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@jcsteh @ScottChesworth @joseonce @Carlos-EstebanM @ElCrackLoko