Docs

[aw]

When using Woocommerce set with the English (Australia) localisation. Woocommerce localisation file is set to replace all occurrences of “cart” with “basket”. (Don’t ask me why, in Australia we know what a cart is…)

However, it appears that X Theme overrides this configuration in woocommerce/cart/cart-empty.php and this line: <?php _e( 'Your cart is currently empty.', '__x__' ) ?>

Just posting this here in case it’s a bug or intentional or can be worked around another way.

[Rue Nel]

Hello There,

Thanks for writing in! Most of the keywords in X theme is using American English. That also includes the WooCommerce template overrides in X. If you selected English (Australia) in the general settings (http://i.prntscr.com/6f02b1d173b14ba88aa53b8d0a8e7527.png), you should translate X as well. To do the properly translation, please check out our knowledge base here: https://community.theme.co/kb/translation/

Please let us know how it goes.

[aw]

Thanks for the reply.

Woocommerce ships with maintained translation files, so can you help me understand why X theme would define a alternate translation for the same string instead of just re-using the Woocommerce translation? Then surely translation for Woocommerce “would just work” whatever language was selected.

Could it just be as simple as using: ‘woocommerce’ instead of ‘__x__’ ?

Same would apply for the other plugins that X theme is overriding.

Is there a really good reason for doing this?

[Rad]

Hi there,

There is no restriction, you may edit the templates and use your preferred textdomain. The purpose of this is to translate them whichever textdomain they are called. If you prefer translating them with woocommerce text domain then please copy /woocommerce/ folder from X main theme to X child theme, then replace the textdomain.

It’s to isolate it from other textdomain, but regardless, you’ll still need them to translate at once since they are from different authors. Example, there is no way users would only translate the plugin in entire development, they will translate the theme too.

Thanks.

[aw]

Thanks for the reply.

What I was trying to understand was why X Theme would create a new “textdomain” when overriding an existing Plugin (in this case Woocommerce) when that Plugin has an existing “textdomain” with extensive translations already implemented.

It seems to be undoing the work previously completed translating the plugin. You effectively have to translate it again.

[Christian]

Hey there,

This is because the template files being overridden are X’s though connected to WooCommerce.

As said previously, you’ll need to translate X as well as generally, you will need to translate both themes and plugins. But, if you want or need to use WooCommerce’s text domain, you can override the template files.

Thanks.

[Author]

Posts