-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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.
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
Payment provider name inconsistently translated #1923
Comments
PayPal etc probably are brands.. not translatable word? not sure though.. |
Right, but Stripe should probably not be translated, as well as Braintree. |
"Example Payment Method" could be translated, since it's not brand |
True. Is there a translation in i18n? |
|
I actually think you need to leave a message for their support, I think that we paid for some translations that were never fulfilled... |
I have been working in Lingo hub to set up "Terms" which you can specify global translations but I keep getting distracted or need to ask their support a question so I get delayed a day to wait for their response. So progress is happening, just super slowly. |
I didn't finish this in time for the 1.1.1 release so moving to 1.2 |
@spencern this is the issue where the payment providers were being corrected (discussed re: #2167) @zenweasel issue with LingoHub is now resolved, and these translations can also be fixed there. |
So I added terms for items below and marked them "untranslatable". That seems to work well. I just don't know how to trigger a PR from that change. I have a question in with support. But that seems like it will take care of it. Let me know if you think of more: Authorize.net |
Closed via #2218 |
Expected behavior
All payment provider names should either be translated or not translated (probably not translated?)
Actual Behavior
Some are and some are not.
Steps to Reproduce the Behavior
The text was updated successfully, but these errors were encountered: