Change Details

On Wikipedia, km² is impossible to target in a search, as is mm³. With unicode digits **regex can find one-character or two-character strings only.** To see this without running bare regex on millions of pages, [Here's 10k pp with 250 unicode hits. Add your own chars 'til it fails.](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³/+prefix:Che&fulltext=Search) On Goggle [[//www.google.com/search?q="mm³"+site:en.wikipedia.org | "mm³" ]] gives 71 results, finding mm³. T41501 says unicode quotes are not normalized, and this one says ² and ³ are not normalized. But //digits are indexed// and quotes are not. T95849 considers analyzers, filtering, and fields, and shows enwiki page mapping properties while troubleshooting the unicode ★ character. But the black star [is found in regex strings,](//en.wikipedia.org/w/index.php?search=insource:/"{{Unicode|★}}+||+U%2B2605"/+prefix:Miscellaneous&title=Special:Search&go=Go) and other unicode characters are also found in regex strings. The //highlighter analyzer// works correctly "finding" unicode digits in all manner of strings. For example, [see `insource:/²|³|km²/ prefix:Che`](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³|km²/+prefix:Che&fulltext=Search). Km² is "found" by the **highlighter**, but when you remove the //actual// matches (single unicode strings) `²|³`... nothing. The //typeahead analyzer// works fine for or mm³ or km². Summary concerning the most basic search for unicode digits: - `"mm3"` or `"km2"` find no normalized ² or ³ character in the index. - `"mm³"` or `"m²"` find only mm or m (because these digits are treated as punctuation?) - `insource:/mm³/` or `insource:/km²/` find nothing because they're greater than two chars. - These problems do not exist for other unicode characters, just digits.

On Wikipedia, km² is impossible to target in a search, yet Goggle reports [[//www.google.com/search?q="km²"+site:en.wikipedia.org | "km²" ]] on well over 120,000 pages. But Unicode **digits** - **have not been normalized**. Basic search `"mm3"` or `"km2"` find no normalized ² or ³ character in the index. - **are treated like punctuation**. Basic search `"mm³"` finds `mm`. - **fail in regex strings greater than two chars**. `/mm³/` or `/km²/` are missing out. Major templates such as Convert and Val supports unicode digits in either form `km²` or `km2`. In mainspace, 5% of pages who use `<sup>2` also use `²`. Confusingly, km² is recognized by the **highlighter**, but when you remove the //actual// matches (single unicode strings) `²|³`... nothing. For example, [see `insource:/²|³|km²/ prefix:Chem`](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³|km²/+prefix:Chem&fulltext=Search). Also the //typeahead analyzer// works fine for or mm³ or km². To see how two is ok but three fails, and without running bare regex on millions of pages, [here's a small domain with some /²|³/ hits.](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³/+prefix:Chem&fulltext=Search) T41501 says unicode quotes are not normalized, and this one says ² and ³ are not normalized. But //digits are indexed// and quotes are not. T95849 considers analyzers, filtering, and fields, and shows enwiki page mapping properties while troubleshooting the unicode ★ character. But the black star, although not found in indexed searches, [is not impossible to find using regex](//en.wikipedia.org/w/index.php?search=insource:/"{{Unicode|★}}+||+U%2B2605"/+prefix:Miscellaneous&title=Special:Search&go=Go), and other unicode characters are also found in regex strings.

On Wikipedia, km² is impossible to target in a search, as is mm³. With unicode digits **regex can find one-character or two-character strings only.** To see this without running bare regex on millions of pages, [Here's 10k pp with 250 unicode hits. Add your own chars 'til it fails.](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³/+prefix:Che&fulltext=Search) On Goggleyet Goggle reports [[//www.google.com/search?q="mm³q="km²"+site:en.wikipedia.org | "mm³" ]] gives 71 results, finding mm³. T41501 says unicode quotes are not normalized, and this one says ² and ³ are not normalized. But //digits are indexed// and quotes are not. T95849 considers analyzers, filtering, and fields, and shows enwikikm²" ]] on well over 120,000 pages. But Unicode **digits** page mapping properties while troubleshooting the unicode ★- **have not been normalized**. Basic search `"mm3"` or `"km2"` find no normalized ² or ³ character in the index. But the black star [is found in regex strings,](//en.wikipedia.org/w/index.php?search=insource:/"{{Unicode|★}}+||+U%2B2605"/+prefix:Miscellaneous&title=Special:Search&go=Go) and other unicode characters are also found in regex strings- **are treated like punctuation**. Basic search `"mm³"` finds `mm`. The //highligh- **fail in regex strings greater analyzer// works correctly "finding"than two chars**. `/mm³/` or `/km²/` are missing out. Major templates such as Convert and Val supports unicode digits in all manner of strings.either form `km²` or `km2`. In mainspace, For example,5% of pages who use `<sup>2` also use `²`. [see `insource:/²|³|km²/ prefix:Che`](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³|km²/+prefix:Che&fulltext=Search). Km² is "found" by the **highlighter**, Confusingly, km² is recognized by the **highlighter**, but when you remove the //actual// matches (single unicode strings) `²|³`... nothing. TFor example, [see `insource:/²|³|km²/ prefix:Chem`](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³|km²/+prefix:Chem&fulltext=Search). Also the //typeahead analyzer// works fine for or mm³ or km². Summary concerning the most basic search for unicode digits: - `"mm3"` or `"km2"` find no normalized ² or ³ character in the index. - `"mm³"` or `"m²"` find only mm or m (because these digits are treated as punctuation?) - `insource:/mm³/` or `insource:/km²/` find nothing because they're greater than two charsTo see how two is ok but three fails, and without running bare regex on millions of pages, [here's a small domain with some /²|³/ hits.](https://en.wikipedia.org/w/index.php?title=Special:Search&profile=default&search=insource:/²|³/+prefix:Chem&fulltext=Search) T41501 says unicode quotes are not normalized, and this one says ² and ³ are not normalized. But //digits are indexed// and quotes are not. T95849 considers analyzers, filtering, and fields, and shows enwiki page mapping properties while troubleshooting the unicode ★ character. - These problems do not exisBut the black star, although not for other unicode charactersund in indexed searches, just digit[is not impossible to find using regex](//en.wikipedia.org/w/index.php?search=insource:/"{{Unicode|★}}+||+U%2B2605"/+prefix:Miscellaneous&title=Special:Search&go=Go), and other unicode characters are also found in regex strings.