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.

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

Closed
zenweasel opened this issue Feb 28, 2017 · 12 comments
Closed

Payment provider name inconsistently translated #1923

zenweasel opened this issue Feb 28, 2017 · 12 comments
Assignees
Labels
bug For issues that describe a defect or regression in the released software
Projects

Comments

@zenweasel
Copy link
Collaborator

zenweasel commented Feb 28, 2017

Expected behavior

All payment provider names should either be translated or not translated (probably not translated?)

Actual Behavior

Some are and some are not.
reaction

Steps to Reproduce the Behavior

  1. Log in as an admin
  2. Go to Payment in the dashboard
  3. Set language to be something besides English
  4. Observe that some payment providers are translated, some are not.
@aaronjudd
Copy link
Contributor

PayPal etc probably are brands.. not translatable word? not sure though..

@zenweasel
Copy link
Collaborator Author

Right, but Stripe should probably not be translated, as well as Braintree.

@zenweasel
Copy link
Collaborator Author

"Example Payment Method" could be translated, since it's not brand

@aaronjudd
Copy link
Contributor

True. Is there a translation in i18n?

@zenweasel
Copy link
Collaborator Author

[{
  "language": "Arabic",
  "i18n": "ar",
  "ns": "reaction-stripe",
  "translation": {
    "reaction-payments": {
      "admin": {
        "shortcut": {
          "stripeLabel": "شريط"
        },
        "dashboard": {
          "stripeLabel": "شريط",
          "stripeDescription": "المدفوعات شريط"
        },
        "paymentSettings": {
          "stripeLabel": "شريط",
          "stripeSettingsLabel": "شريط",
          "stripeSettingsDescription": "لم يكن لديك معرف العميل الشريط API؟",
          "stripeSettingsGetItHere": "أحضره هنا"
        }
      }
    }
  }
}]

@aaronjudd aaronjudd added this to the v1.0.0 milestone Mar 14, 2017
@zenweasel zenweasel self-assigned this Apr 5, 2017
@zenweasel
Copy link
Collaborator Author

Trying to change these in LingoHub (I had already modified a bunch of these in code but some I can't really fix). But when I go into LingoHub the word shows as "locked" with the status "ordered". Have a support request in with LIngoHub

editor___lingohub

@aaronjudd
Copy link
Contributor

I actually think you need to leave a message for their support, I think that we paid for some translations that were never fulfilled...

@zenweasel
Copy link
Collaborator Author

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.

@zenweasel
Copy link
Collaborator Author

I didn't finish this in time for the 1.1.1 release so moving to 1.2

@zenweasel zenweasel modified the milestones: v1.2.x, v1.0.x Apr 21, 2017
@aaronjudd
Copy link
Contributor

@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.

@zenweasel
Copy link
Collaborator Author

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
Braintree
PayPal/PayPal Express/ Paypal Pro
Shippo
Stripe
Avalara
TaxCloud

@aaronjudd aaronjudd added the bug For issues that describe a defect or regression in the released software label Apr 27, 2017
@zenweasel
Copy link
Collaborator Author

Closed via #2218

@aaronjudd aaronjudd added this to Done in Core Jul 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug For issues that describe a defect or regression in the released software
Projects
No open projects
Core
Done
Development

No branches or pull requests

2 participants