[Resolved] Translating numbers

Sendbox is not allowing me to save the translation of the line "01.01.2024" at all with the following message: "The original sentence includes formatting markers. However, not all markers are applied to the translation". I don't have any markers in this text. I am using the classic editor, which shows all the code. And WPML does not show any markers.

I was talking about the WP classic editor. I use ATE with the WPML. Can _you_ translate my string using ATE?

I reproduced the error on a second-level page when the URL is escaped and relatively long - using Bulgarian as an example (this, as I know from experience, is one of the main problems with WPML, which seems to be focused mainly on languages built exclusively or predominantly on characters that don't require escape and, consequently, URLs on which are much shorter than those for which all characters require escape). I haven't tried this on a first-level page, but I wouldn't rule out reproducing the error on a sufficiently long URL there as well.

Sumit,

I can't confirm that.

It's about translating numbers when the original and the translation are different. For example, when "01.01.2024" is translated as "01/01/24".

Please note that the error occurs when the URL of the original page (this is about translating pages, not posts, I'm not sure how it works with posts) contains escapered characters, this is important. In other words, different in that it contains % characters, not just slash-dash-underscores, Latin letters and so-called Arabic numerals. Perhaps (this is just an idea), this is the reason for the problem, because the use of this very % symbol is not specified somewhere (this is not such a rare problem in programming). I have described in detail above how to reproduce the error. Note that I pointed out the need to switch to a language that uses non-Latin characters (or not only them), such as Bulgarian or other Cyrillic language.

I first reported this problem in one of my support tickets as far back as two years ago. Then it was part of the problem that absolutely everything that was translated via search-box in ATE was not saved when the original was updated if (if!) the original URL contained escaped characters and was not top-level (I don't remember if we checked whether this error would recur if the URL was sufficiently long at the top level, but it seems we could reproduce the error even when the URL did not contain escaped characters but was somewhere around the fourth or so level). Anyway, with one of the recent changes, this problem has been fixed (after two years!), but NOT the digits part, which is what I reported in this ticket.

Here's an example of what exactly I'm facing because of that. Right now, I had to update a page on my website that has a table with about 140 dates in DD.MM.YYYYY format. This page is translated into 39 languages. 26 of them have a different date format. And I need to make 140 x 26 = 3640 changes to these 26 pages (the changes are different on different pages and are all done manually; and they will be erased if I need to update the page again!). This is the eighth such page I'm working with. The others have had about the same number of changes, so you can imagine the extent of the problem for me personally.

(By the way, although, as I wrote above, a change was recently made to allow changes made via search-box to be saved permanently if they are NOT only-digits strings, I should add that this change did not fix the problem with deleting any other such changes if the page is large enough, i.e. if there is literally a lot of text on it. I have 8 pages of roughly the same format, distinguished only by the fact that one of them contains several times as much text. On this page, ANY search-box translated text continues to be deleted when I modify the original page. I have it translated into 39 languages too. These search-box translations are translations of anchors, because WPML does not require translation of anchors, just like it does not require translation of URLs, but URLs change from language to language automatically, while anchors do not. So I am forced to translate them via search-box).

Unfortunately, the sandbox of this ticket is no longer available. There, however, I reproduced the problem with just this simple example: "01.01.2004". To do this, I switched WP to Bulgarian, created a page in Bulgarian and translated it into, I think, English (it could be any other), for example, like this: "01/01/2004", saved the translation, then made changes to the original page and observed that the above translation was not saved, missing when opening ATE. I would gladly do what you are asking if I had ATE working for me. Unfortunately it doesn't, no translation opens (I am returned to my site with the message: "Our session has expired, please log in again" even after changing the WPML key and restoring the site to the version before the problem occurred, which is the subject of my other ticket today(((( However, if ATE works for me, I will certainly do what you ask.