I wrote a delivery date with dots like 15.09.2026 and its digits weren't converted; why?

What the tool saw

Protection looks for text patterns that would break if their digits changed: links, emails, IP addresses such as 192.168.1.10, and version numbers such as 2.4.1. That last pattern has a simple definition: a number, a dot, a number, a dot, a number, possibly repeated. The tool has no idea 15.09.2026 is a date; to it, this is a three-part version number.

The result with the defaults, Arabic-Indic target and protection on:

موعد التسليم 15.09.2026

Not one digit converted. The tool shows 8 under 'Digits protected', and the protected tokens line lists 15.09.2026 itself. That is the key to understanding it: whenever a digit you expected to convert did not, look at that list first.

Three fixes, and which to pick

The first and safest fix is to change how the date is written. A slash matches none of the protected patterns:

موعد التسليم ١٥/٠٩/٢٠٢٦

Eight digits converted. Dashes work the same way and give ١٥-٠٩-٢٠٢٦.

The second fix is to switch protection off. All eight digits convert and the dots stay, giving ١٥.٠٩.٢٠٢٦. But any link or IP address in the same text will have its digits converted too, so only do this for text that has none.

The third is not a fix but a trap: protection off with the separator option on. The two dots between digits become Arabic decimal separators, giving ١٥٫٠٩٫٢٠٢٦, which reads as an odd decimal number rather than a date. Before you switch it on, the tool reports that two decimal points would change; take that number seriously.

Steps for the first fix

1. In the original text, replace the dots in dates with slashes. In a long text use your editor's find and replace, but check it did not touch decimal prices.
2. Open the Arabic/Persian/Western digit converter, paste the text, and choose Arabic-Indic.
3. Keep protection on, and confirm the date is no longer in the protected tokens list.
4. Copy the result.

Other things that can get protected by accident

• Item or section numbers written with two dots, such as 3.2.1.
• Times written with dots instead of colons, such as 10.30.15.
• Any number in four dot-separated parts, because it looks like an IP address.

An ordinary decimal such as 18.50 is not protected, because it has a single dot, so it converts to ١٨.٥٠.