This topic has 15 replies, 2 voices, and was last updated 6 years, 2 months ago ago by Rose Tyler
Hey,
can you help me with the translation, pls?^^
1) So first I would like to know how I translate Share into German:
2) I think you have nothing to do with the credit card translation. It’s from the “Stripe plugin”. But I absolutely do not understand why this is not translated.
Maybe and just mabye you have time to look? You have much more know how than me. I Would spend hours finding the mistake..
3) For the wish list, only the title is not translated. Where can I translate this?
4) Shopping cart the same. How can I translate “shopping cart” and “order complete”?
5) Here’s another case where I think you have nothing to do with “AmazonPay”. Correct me if I’m wrong.
Same as with “Stripe”. I can not understand why it is not translated.
I guess I’m just stupid, because I’m not quite right with “loco translate” right. Are the complications perhaps due to child-theme?
Regards
Joey 🙂
Hello,
1. http://prntscr.com/kp0khs
2. Try to clear cache to be sure that the problem is not caused by cache.
Also, I would recommend you to contact the plugin author.
3. Please edit title of the page http://prntscr.com/kp0trf
4. You need to synchronize translation files http://prntscr.com/kp1jid then you will be able to find and translate required strings.
Button Sync allows you to synchronize your translation file with updated pot file. It means if we made any changes in template files that may affect transaltion or we added new string for the translation and you updated theme you need to synchronize your translation with updated files. Only after synchronization, you’ll be able to translate new strings or strings that were changed.
5. Please contact authors of the plugin.
Regards
Ok, thank u Rose!
A few more little question^^
1) I do not know why the word “remove” is not translated.
I already translated it..
2) Can I have the fields on the right as well as the links on the “Login”? So not next to each other? I do not know how to articulate in English. The input fields under the labels?
3) How can I position the text next to the second checkbox? So like the first checkbox. Its the Checkout-Page:
Thanks in advance
Joey
*Supplement to 2)
Sorry for the delay due to the weekends.
1. Thanks for the notice. We will fix it in next theme update. As a temporary solution, you can change “Remove” text in wp-content/themes/xstore/woocommerce/cart/cart.php http://prntscr.com/kpxwwr
2. Woocommerce > Settings > Accounts & Privacy > Account creation > When creating an account, automatically generate a username from the customer’s email address.
3. Please use this custom css code:
.checkout input[type="checkbox"] + label {
padding-left: 20px;
}
.checkout input#shipping-service-provider {
position: absolute;
}
Regards
First of all, thank you.
In 2) I actually meant something else. In their preview, the input fields are among the labels. For me, the fields are next to each other. ^^
Regards
You’re welcome!
2. Please add this custom css:
.woocommerce-account form.register input {
max-width: 100%;
}
Regards
It is now a bit offset
Regards
Joey
Oh I see, add this also:
.woocommerce-account .woocommerce-form-register {
max-width: 500px;
margin: 0 auto;
}
Regards
Great, thank u!
Is it also possible to bring the product-information on one level with the product-image?
Currently it looks like this:
Is it possible, that it would looks like this on desktop?
Regards
You’re welcome!
@media only screen and (min-width: 1200px){
.single-product .product-information {
margin-top: 5%;
}
}
Regards
Thank you.
I know it’s only minor things, but how can I get the checkbox when paying with credit cards to a height with the word “Kredit Karte”?
“CheckOut-Page”
Regards
Joey
Please try this code:
.woocommerce-checkout #payment .payment_method_stripe label[for=payment_method_stripe] {
padding-left: 21px;
margin-top: 10px;
}
.woocommerce-checkout #payment input#payment_method_stripe {
margin-top: 6px;
}
Regards
Alright, thank u very much
You’re welcome!
Have a nice day.
Regards
The issue related to '‘translation-issues’' has been successfully resolved, and the topic is now closed for further responses