Transliteration
Universal Unicode ➡ Latin transliteration / slugify module. Works with all major languages and on all platforms.
Demo
Try it out
Compatibility / Browser support
IE 9+ and all modern browsers.
Other platforms including Node.js, Web Worker, ReactNative and CLI
Install
Node.js / React Native
npm install transliteration --save
import { transliterate as tr, slugify } from 'transliteration';
tr('你好, world!');
slugify('你好, world!');
Browser (CDN):
<script async defer src="https://cdn.jsdelivr.net/npm/transliteration@2.0.4/dist/browser/bundle.umd.min.js"></script>
<script>
console.log(transliterate('你好'));
</script>
<script type="module">
import { transliterate } from 'https://cdn.jsdelivr.net/npm/transliteration@2.0.4/dist/browser/bundle.esm.min.js';
console.log(transliterate('你好'));
</script>
transliteration
can be loaded as an AMD / CommonJS module, or as global variables (UMD).
When using it in the browser, by default it creates global variables under window
object:
transliterate('你好, World');
slugify('Hello, 世界');
CLI
npm install transliteration -g
transliterate 你好
slugify 你好
echo 你好 | slugify -S
Usage
transliterate(str, [options])
Transliterates the string str
and return the result. Characters which this module doesn't recognise will be defaulted to the placeholder from the unknown
argument in the configuration option, defaults to ''
.
Options: (optional)
{
ignore?: string[];
replace?: OptionReplaceCombined;
replaceAfter?: OptionReplaceCombined;
trim?: boolean;
unknown?: string;
}
transliterate.config([optionsObj], [reset = false])
Bind options object globally so any following calls will be using optoinsObj
as default. If optionsObj
is omitted, it will return current default options object.
import { transliterate as tr } from 'transliteration';
tr('你好,世界');
tr('Γεια σας, τον κόσμο');
tr('안녕하세요, 세계');
tr('你好,世界', { replace: {你: 'You'}, ignore: ['好'] });
tr('你好,世界', { replace: [['你', 'You']], ignore: ['好'] });
tr.config({ replace: [['你', 'You']], ignore: ['好'] });
tr('你好,世界')
console.log(tr.config());
tr.config(undefined, true);
console.log(tr.config());
slugify(str, [options])
Convert Unicode str
into a slug string for making sure it is safe to be used in an URL as a file name.
Options: (optional)
ignore?: string[];
replace?: OptionReplaceCombined;
replaceAfter?: OptionReplaceCombined;
trim?: boolean;
unknown?: string;
lowercase?: boolean;
uppercase?: boolean;
separator?: string;
allowedChars?: string;
slugify.config([optionsObj], [reset = false])
Bind options globally so any following calls will be using optoinsObj
by default. If optionsObj
argument is omitted, it will return current default option object.
import { slugify } from 'transliteration';
slugify('你好,世界');
slugify('你好,世界', { lowercase: false, separator: '_' });
slugify('你好,世界', { replace: {你好: 'Hello', 世界: 'world'}, separator: '_' });
slugify('你好,世界', { replace: [['你好', 'Hello'], ['世界', 'world']], separator: '_' });
slugify('你好,世界', { ignore: ['你好'] });
slugify.config({ lowercase: false, separator: '_' });
slugify('你好,世界');
console.log(slugify.config());
slugify.config({ replace: [['你好', 'Hello']] });
slugify('你好, world!');
console.log(slugify.config());
slugify.config(undefined, true);
console.log(slugify.config());
If the variable names conflict with other libraries in your project or you prefer not to use global variables, use noConfilict() before loading libraries which contain the conflicting variables.:
CLI
➜ ~ transliterate --help
Usage: transliterate <unicode> [options]
Options:
--version Show version number [boolean]
-u, --unknown Placeholder for unknown characters [string] [default: ""]
-r, --replace Custom string replacement [array] [default: []]
-i, --ignore String list to ignore [array] [default: []]
-S, --stdin Use stdin as input [boolean] [default: false]
-h, --help [boolean]
Examples:
transliterate "你好, world!" -r 好=good -r Replace `,` into `!`, `world` into `shijie`.
"world=Shi Jie" Result: Ni good, Shi Jie!
transliterate "你好,世界!" -i 你好 -i , Ignore `你好` and `,`.
Result: 你好,Shi Jie !
➜ ~ slugify --help
Usage: slugify <unicode> [options]
Options:
--version Show version number [boolean]
-U, --unknown Placeholder for unknown characters [string] [default: ""]
-l, --lowercase Peturns result in lowercase [boolean] [default: true]
-u, --uppercase Returns result in uppercase [boolean] [default: false]
-s, --separator Separator of the slug [string] [default: "-"]
-r, --replace Custom string replacement [array] [default: []]
-i, --ignore String list to ignore [array] [default: []]
-S, --stdin Use stdin as input [boolean] [default: false]
-h, --help [boolean]
Examples:
slugify "你好, world!" -r 好=good -r "world=Shi Replace `,` into `!` and `world` into
Jie" `shijie`.
Result: ni-good-shi-jie
slugify "你好,世界!" -i 你好 -i , Ignore `你好` and `,`.
Result: 你好,shi-jie
Change log
2.1.0
- Added
transliterate
as global variable for browser builds. Keep transl
for backward compatibility.
2.0.0
- CDN file structure changed: https://www.jsdelivr.com/package/npm/transliteration
- The entire module had been refactored in Typescript, with big performance improvements as well as a reduced package size.
- Better code quality. 100% unit tested.
bower
support was dropped. Please use CDN or webpack
/rollup
.- As according to RFC 3986, more characters(
/a-zA-Z0-9-_.~/
) are kept as result for slugify
, and it is configurable. - Added
uppercase
as an option for slugify
, if is set to true
then the generated slug will be converted to uppercase letters. - Unknown characters will be transliterated as empty string by default, instead of a meaningless
[?]
.
1.6.6
- Added support for
TypeScript
. #77
1.5.0
- Minimum node requirement: 6.0+
1.0.0
- Code had been entirely refactored since version 1.0.0. Be careful when you plan to upgrade from v0.1.x or v0.2.x to v1.0.x
- The
options
parameter of transliterate
now is an Object
(In 0.1.x it's a string unknown
). - Added
transliterate.config
and slugify.config
. - Unknown string will be transliterated as
[?]
instead of ?
. - In the browser, global variables have been changed to
window.transl
and windnow.slugify
. Other global variables are removed.
Caveats
Currently, transliteration
only supports 1 to 1 code map (from Unicode to Latin). It is the simplest way to implement, but there are some limitations when dealing with polyphonic characters. It does not work well with all languages, please test all possible situations before using it. Some known issues are:
-
Chinese: Polyphonic characters are not always transliterated correctly. Alternative: pinyin
.
-
Japanese: Most Japanese Kanji characters are transliterated into Chinese Pinyin because of the overlapped code map in Unicode. Also there are many polyphonic characters in Japanese which makes it impossible to transliterate Japanese Kanji correctly without tokenizing the sentence. Consider using kuroshiro
for a better Kanji -> Romaji conversion.
-
Thai: Currently it is not working. If you know how to fix it, please comment on this issue.
-
Cylic: Cylic characters are overlapped between a few languages. The result might be inaccurate in some specific languages, for example Bulgarian.
If you there's any other issues, please raise a ticket.
License
MIT