Skip Navigation

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

This topic contains 4 replies, has 2 voices.

Last updated by Waqas Bin Hasan 1 year, 9 months ago.

Assisted by: Waqas Bin Hasan.

Author Posts
February 23, 2023 at 1:57 pm #13100111

TomasB

See images. 2 questions. Seems like bad UX/concept in general. Could you please provide (alternative) solutions to these issues? Or address them in an update?

SCR-20230223-kn6-2.png
SCR-20230223-kj2-2.png
February 24, 2023 at 9:53 am #13106709

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting the support.

For that "sup" marker issue, there's no alternate solution at the moment, except the way you already handled it. However, I've filed a feature request to the 2nd tier for a review. I'll update you on it once I hear back.

For the other issue regarding skipping a text, you can join the sentences and can skip the text you don't want to translate, during the translation of the joined text. See https://wpml.org/documentation/translating-your-contents/advanced-translation-editor/#joining-sentences for details.

Regards.

February 24, 2023 at 9:58 am #13106779

TomasB

Hello Waqas,

thank you for looking into it. My UX opinion would be:

1. Have markers optional and not require all/any of them to be selected.

2. Allow sentences to have a blank translation.

This is just from my point of view, maybe you found reasons why the above is not good/possible.

February 24, 2023 at 12:20 pm #13107957

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Sure thing, noted with thanks.

I'll update you with details once I hear back from the team.

Have a nice weekend!

February 27, 2023 at 4:50 am #13119257

Waqas Bin Hasan
Supporter

Languages: English (English )

Timezone: Asia/Karachi (GMT+05:00)

Hi,

Thank you for waiting. Our team is already aware of the said issues and suggests that you can use . [dot] and add the marker to this dot then add CSS to hide this dot on front-end:

html[lang="fi"] sup {
	display: none;
}

This is the only workaround for now while the issues being taken care by the relevant teams. There's no ETA for now, but probably you may find these fixed in a future version.

Regards.