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.
Tagged: Exception
Author | Posts |
---|---|
December 13, 2023 at 8:23 pm #15058799 | |
John-Pierre Cornelissen |
Hello, I have translated the site with "Translate Everything Automatically". When reviewing the translations, I found that certain words are consistently translated wrong. I have added them to the glossary now. 1) Is there a way to let the system automatically fix existing mistakes based on the new glossary items? Or do I have to manually do that for each page. 2) Will new translations automatically use the glossary items from now on? As for adding terms to the glossary 3) Do I have to add singular and plural terms in the glossary? Or do I add it as singular after which it understands the plural? Example Dutch » English: 4) Does it automatically capitalize words when needed. So a term is: Thanks |
December 15, 2023 at 4:24 pm #15074981 | |
Alejandro Supporter
Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+01:00) |
Hello! I'll help you get started while a supporter takes your case. 1) You will have to open each page and fix them yourself. we are about to release a new feature that will do what you want (update the translation when you add or change the glossary) but it will only do that with the content made up to 30 days from that moment. the feature is estimated to be rolled out more or less in sync with 4.6.9, at this point not before mid january 2024. 2) The new translations will use the glossary term, yes. remember that if you have CAT, then the element in the page needs to be CAT as well, not "cat" or "Cat" or any other variation. 3) You need to add both. 4) No, refer to the last phrase in my step 2. you can try it as a general term instead and it will use that as a reference, it might work that way but it greatly depends on the translation engine, we send it as a reference to them and it's up to them to decide whether to use it or not. |
December 15, 2023 at 4:33 pm #15075111 | |
John-Pierre Cornelissen |
Thank you for explaining Alejandro. As for #4, in this case the translation engine is your own ATE. Will it do that? If not, can you add it as a feature request? Otherwise it means you basically have to enter every glossary term twice, one with and one without capital. I'd say, it should only capitalize the first character at the start of a sentence if the glossary term is all lower case. If the term is mixed or all upper case it should keep it that way. Thanks |
December 18, 2023 at 9:10 am #15081421 | |
Dražen Supporter
Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00) |
Hello JP, thanks for getting back. ATE is a translation editor, but the engine behind it is DEEPL, Google, or Microsoft, depending on your settings. We have some plans to work on improving these cases from our side, and we will do our best to improve it. As for parts that are not directly affected by our system, for example, glossaries from DEEPL we have no control then there is not much we can do. Please follow our news for any new improvements in the future. Regards. |
December 18, 2023 at 9:33 am #15081563 | |
John-Pierre Cornelissen |
Thank you Drazen, For my understanding how it works, does it mean that the Glossary that is created in WPML is being sent to the engine with each translation request? Maybe it's possible to do it programmatically by automatically adding the variants. So if I enter term It will automatically add the terms term 😉 Thanks |
December 18, 2023 at 1:52 pm #15084747 | |
Dražen Supporter
Languages: English (English ) Timezone: Europe/Zagreb (GMT+01:00) |
Hello JP, sure, our team as I said has some plans to improve small and large capital letters in sentences and glossary. I can not share much more info on that and the methods going to be used. As for how the glossary works, yes it is sent each time as part of your translation job. Regards, |
December 18, 2023 at 2:30 pm #15085131 | |
John-Pierre Cornelissen |
Ok, thanks for explaining |