Skip to content
Skeleton algorithm from Unicode TR39 for testing confusability of strings
Java
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.m2
tr39-confusables-skeleton
tr39-confusables-table-generator-maven-plugin
.gitignore
.travis.yml
LICENSE
README.md
pom.xml

README.md

tr39-confusables Maven Central Build Status

Skeleton algorithm from Unicode TR39 for testing confusability of strings.

Version 8.0.10 matches version 8.0 draft 10 of TR39

Usage

import static com.github.mpkorstanje.unicode.tr39confusables.Skeleton.skeleton;
...
// Skeleton representations of unicode strings containing 
// confusable characters are equal 
skeleton("paypal").equals(skeleton("paypal")); // true
skeleton("paypal").equals(skeleton("𝔭𝒶ỿ𝕡𝕒ℓ")); // true
skeleton("paypal").equals(skeleton("ρ⍺у𝓅𝒂ן")); // true
skeleton("ρ⍺у𝓅𝒂ן").equals(skeleton("𝔭𝒶ỿ𝕡𝕒ℓ")); // true
skeleton("ρ⍺у𝓅𝒂ן").equals(skeleton("𝔭𝒶ỿ𝕡𝕒ℓ")); // true

// The skeleton representation does not transform case
skeleton("payPal").equals(skeleton("paypal")); // false

// The skeleton representation does not remove diacritics
skeleton("paypal").equals(skeleton("pàỳpąl")); // false

Note on the use of Skeleton, from TR39:

A skeleton is intended only for internal use for testing confusability of strings; the resulting text is not suitable for display to users, because it will appear to be a hodgepodge of different scripts. In particular, the result of mapping an identifier will not necessary be an identifier. Thus the confusability mappings can be used to test whether two identifiers are confusable (if their skeletons are the same), but should definitely not be used as a "normalization" of identifiers.

Maven

<dependency>
  <groupId>com.github.mpkorstanje</groupId>
  <artifactId>tr39-confusables-skeleton</artifactId>
  <version>8.0.10</version>
</dependency>
You can’t perform that action at this time.