Giter VIP home page Giter VIP logo

japanese.js's Introduction

japanese.js NPM version Build Status Coverage Status Dependency Status Greenkeeper badge

Util collection for Japanese text processing. Hiraganize, Katakanize, and Romanize.

Install

$ npm install --save japanese

Usage

var japanese = require('japanese');

japanese.hiraganize('ヱヴァンゲリヲン');

For crazy syntax sugar junkies:

var japanese = require('japanese/sugar');

'ヱヴァンゲリヲン'.hiraganize();

Command

Command Line Interface is also available.

$ npm install japanese -g
$ japanese

  Util collection for Japanese text processing. Hiraganize, Katakanize, and Romanize.

  Usage:
    japanese <input> [options]

  Options:
    -h, --hiraganize   hiraganize input string
    -k, --katakanize   katakanize input string
    -r, --romanize     romanize input string

  Example
    japanese ヱヴァンゲリヲン --hiraganize

API

japanese.hiraganize(text)

Convert input katakana into hiragana.

Arguments

  • text The text to hiraganize

Example

japanese.hiraganize('ヱヴァンゲリヲン');     // ゑゔぁんげりをん
japanese.hiraganize('チヨコバナヽ');         // ちよこばなゝ
japanese.hiraganize('ヹルタースオリジナル'); // ゑ゙るたーすおりじなる
japanese.hiraganize('板垣死ス𪜈');           // 板垣死すとも

japanese.katakanize(text)

Convert input hiragana into katakana.

Arguments

  • text The text to katakanize

Example

japanese.katakanize('抹茶あいす');       // 抹茶アイス
japanese.katakanize('ばゞへらあいす');   // バヾヘラアイス
japanese.katakanize('ゐ゙よろん');         // ヸヨロン
japanese.katakanize('本日ゟかき氷解禁'); // 本日ヨリカキ氷解禁

japanese.romanize(text[, config])

Convert input text into romaji.

important: Most definitions of Japanese text romanizations require total recognition of Japanese text, but robots cannot actually think or understand! Some conversions are hopelessly poor. For example, ISO 3602 defines that "こうし" which means "講師" must be romanized as "kôsi", while "こうし" which means "子牛" must be romanized as "kousi" (because 子牛 is mixed word of 子 and 牛), though these are apparently the same in Kana-form. While japanese.js is very... very very thoroughly tested, this module (and any other romanization machines) cannot distinguish between these semantics. So unfortunately, you cannot use this function for official writing or something. Ugh.

Arguments

  • text The text to romanize
  • config The configuration object or string used to romanize. Described below.

Example

japanese.romanize('れんあいかんじょう');       // ren'aikanjō
japanese.romanize('ツァトゥグァ');             // tsatugwa
japanese.romanize('くうぼをきゅう', 'kunrei'); // kûbookyû
japanese.romanize('でんぢゃらす', 'nihon');    // dendyarasu
japanese.romanize('いいづか とおる', {
	'いい': 'ii',
	'おお': 'oh',
});                                            // iizuka tohru

Configs

Config is represented as plain object, where object keys stand for a collection of similar characters, and the value determines how these characters are converted. So the object is not just the same as a conversion table.

Available parameters are following.

Key Available Values
si, shi
ti, chi
tu, tsu
hu, fu
zi, ji
di, zi, ji, dzi, dji
du, zu, dsu, dzu
ああ aa, ah, â, ā, a
いい ii, ih, î, ī, i
うう uu, uh, û, ū, u
ええ ee, eh, ê, ē, e
おお oo, oh, ô, ō, o
あー a-, aa, ah, â, ā, a
えい ei, ee, eh, ê, ē, e
おう ou, oo, oh, ô, ō, o
んあ na, n'a, n-a
んば nba, mba
っち tti, tchi, cchi
i, wi
o, wo

You can also specify these predefined configs by supplying a string. Default is wikipedia.

'wikipedia' 'traditional hepburn' 'modified hepburn' 'kunrei' 'nihon'
shi shi shi si si
chi chi chi ti ti
tsu tsu tsu tu tu
fu fu fu hu hu
ji ji ji zi zi
ji ji ji zi di
zu zu zu zu du
ああ aa aa ā â ā
いい ii ii ii î ī
うう ū ū ū û ū
ええ ee ee ē ê ē
おお ō ō ō ô ō
あー ā ā ā â ā
えい ei ei ei ei ei
おう ō ō ō ô ō
んあ n'a n-a n'a n'a n'a
んば nba mba nba nba nba
っち tchi tchi tchi tti tti
i i i i wi
o wo o o wo

And here are short notes about these romanizations.

Wikipedia style

Source: http://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Japan-related_articles#Romanization

The most modern and widely used form of romanization. Wikipedia uses this guideline to name their article title and text. This is mixed version of traditional and modified Hepburn and easily recognizable for everyone.

Traditional and Modified Hepburn

Source: http://en.wikipedia.org/wiki/Hepburn_romanization

Actually this is not a specification. Hepburn romanization is very widely known but nobody other than Hepburn knows the REAL definition of these method.

Kunrei-shiki and Nihon-shiki

Source: http://www.iso.org/iso/catalogue_detail.htm?csnumber=9029

Kunrei-shiki is defined as ISO 9029 and Nihon-shiki as ISO 9209 Strict. These romanizations are today kind of obsolete but still the only standardized romanization in the world.

Roadmap

  • japanese.deromanize()
  • japanese.cyrillize()
  • japanese.decyrillize()
  • japanese.hangulize()
  • japanese.dehangulize()
  • japanese.arabize()
  • japanese.dearabize()
  • japanese.gyarumojize()
  • japanese.isKatakana()
  • japanese.isHiragana()
  • japanese.isKanji()
  • japanese.isJoyoKanji()
  • japanese.isKinsoku() (JIS X 4051 compatibility is preferred)
  • CLI
    • --input <file> and --output <file> option
    • japanese --hiraganize <string> to work

...and any proposal or idea for enhancing japanese.js is welcomed! Tell me, tell me, tell me!

License

MIT © hakatashi

japanese.js's People

Contributors

greenkeeper[bot] avatar greenkeeperio-bot avatar hakatashi avatar nihey avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar

japanese.js's Issues

An in-range update of jshint is breaking the build 🚨

Version 2.9.5 of jshint just got published.

Branch Build failing 🚨
Dependency jshint
Current Version 2.9.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As jshint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes JSHint 2.9.5

2.9.5 (2017-06-22)

Bug Fixes

  • Account for hoisting of importing bindings (bd36953)
  • Add onmessage to vars.worker (540ed85)
  • Added missing "Storage" browser variable (8cfe5ad)
  • Avoid crash when peeking past end of prog (c083866)
  • Avoid false positive (44d9e0b)
  • Close synthetic scope for labeled blocks (5f0f789)
  • Fail gracefully on invalid if syntax (#3103) (8c6ac87)
  • Honor "ignore" file when linting STDIN (d4f83a4)
  • Parse for-in/of head LHS as asnmt target (da52ad9)
  • Removed warning message W041 (#3115) (376fa62)
  • Throw W033 instead of E058 when the ; after a do-while stmt is missing (6907cd4)

Features

Commits

The new version differs by 42 commits.

  • d3d84ae v2.9.5
  • 481cdca Merge branch 'W083'
  • ad7df61 [[TEST]] Update tests to reflect new W083 language
  • 5967e61 [[TEST]] Less ambiguous message for W083
  • cc215bd [[CHORE]] Update Test262
  • e6c89f0 [[CHORE]] Fix bug in test script
  • 5b957f6 Merge pull request #3126 from jugglinmike/for-lhs
  • da52ad9 [[FIX]] Parse for-in/of head LHS as asnmt target
  • b075919 [[FEAT]] Add MediaRecorder to vars.js
  • 24b8c97 Merge pull request #3066 from jugglinmike/asi-dowhile-es6-updated
  • 29c359f Merge pull request #3064 from jugglinmike/improve-yield-messages
  • c083866 [[FIX]] Avoid crash when peeking past end of prog
  • 5f0f789 [[FIX]] Close synthetic scope for labeled blocks
  • 70f9ca2 Merge remote-tracking branch 'jugglinmike/2358-improve-unused-desc'
  • bd36953 [[FIX]] Account for hoisting of importing bindings

There are 42 commits in total.

See the full diff

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of vinyl-source-stream is breaking the build 🚨

Version 1.1.1 of vinyl-source-stream was just published.

Branch Build failing 🚨
Dependency vinyl-source-stream
Current Version 1.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

vinyl-source-stream is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • coverage/coveralls First build on greenkeeper/vinyl-source-stream-1.1.1 at 95.294% Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 4 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of gulp-jshint is breaking the build 🚨

Version 2.1.0 of gulp-jshint was just published.

Branch Build failing 🚨
Dependency gulp-jshint
Current Version 2.0.4
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

gulp-jshint is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 6 commits.

  • 32a25b0 2.1.0
  • 2c57c9f Merge pull request #157 from spalger/remove-gulp-util
  • 5f621f8 vinyl is only used in testing
  • 5eaabdd add yarn.lock file for dev
  • 154180d [gulp-util/PluginError] use plugin-error directly
  • 357ab98 [gulp-util/File] use Vinyl directly

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of gulp-uglify is breaking the build 🚨

Version 3.0.1 of gulp-uglify was just published.

Branch Build failing 🚨
Dependency gulp-uglify
Current Version 3.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

gulp-uglify is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build failed Details

Release Notes v3.0.1

A relatively small maintenance release.

Fixes

  • If the error from UglifyJS contains column information, append this to the error message (alongside the line number).
  • Buffers are now allocated with Buffer.from, ensuring Buffers never have any private information.
  • The Streams callback is only called once, even if a downstream exits in error.
Commits

The new version differs by 10 commits.

  • c92197d 3.0.1
  • 27b26d4 fix(composer): invoke callback only once
  • 2c7f656 tests: import tape-catch to catch thrown errors
  • b2492c4 fix: create safe-buffers
  • a751c5a tests: convert tests to to tape harness
  • 95f17a5 feat(error): add column to error string
  • e2462fa chore(travis): update test matrix
  • 14f1d71 docs(pump): correct grammar
  • 845ae0f chore(license): remove blockquote from license
  • 9c7b1ae docs(README): update links

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of should is breaking the build 🚨

Version 11.2.1 of should just got published.

Branch Build failing 🚨
Dependency should
Current Version 11.2.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As should is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • coverage/coveralls First build on greenkeeper/should-11.2.1 at 90.208% Details

  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 1 commits .

  • 52b984f Fix .match(RegExp) for everything not supported

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of browserify is breaking the build 🚨

Version 14.2.0 of browserify just got published.

Branch Build failing 🚨
Dependency browserify
Current Version 14.1.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
Commits

The new version differs by 5 commits .

  • 18e1d65 14.2.0
  • 0e1a7a0 add cli support for --transform-key to support mode's like production/staging/etc..
  • a5aa660 Merge pull request #1701 from wogsland/doc-fix
  • ae281bc Fixed documentation formatting that was bugging me
  • fe8c57b async test for node 7

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

Spacing between romanized words

Currently when using this module, じしんがはっぴょうされましたjishingahappyōsaremashita, however it would be better if it returned with romanized spacing, like jishin ga happyō saremashita.

Would this be possible?

https://github.com/lovell/hepburn has spacing:
これはテスト。おまえはあほです。ほんとうばか!kore wa tesuto. omae wa aho desu. hontoo baka!

However your module returns
これはテスト。おまえはあほです。ほんとうばか!korehatesuto.omaehaahodesu.hontōbaka

An in-range update of should is breaking the build 🚨

Version 13.2.0 of should was just published.

Branch Build failing 🚨
Dependency should
Current Version 13.1.3
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

should is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 3 commits.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of browserify is breaking the build 🚨

Version 14.1.0 of browserify just got published.

Branch Build failing 🚨
Dependency browserify
Current Version 14.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As browserify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪


Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details

  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 3 commits .

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.


Your Greenkeeper Bot 🌴

An in-range update of coveralls is breaking the build 🚨

Version 3.0.1 of coveralls was just published.

Branch Build failing 🚨
Dependency coveralls
Current Version 3.0.0
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

coveralls is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Release Notes Additional CI support

Maintenance:

Commits

The new version differs by 9 commits.

  • e7ae2bf version bump; logger test fix
  • 9b892bf Verbose use log level debug
  • 9cfb496 Add buildkite support (#177)
  • aa8c257 Done callback waits for unlink in testRepoTokenDetection to prevent race condition (#179)
  • 18c71c2 Fix a mistype in tests: fs.exists -> fs.existsSync (#184)
  • bd667c6 Add Semaphore support (#180)
  • 10d8b3e Update examples to include Jest (#183)
  • 720ee7c Add license (#175)
  • 83ff2cb Add mention about AppVeyor to the README (#164)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of coffee-script is breaking the build 🚨

Version 1.12.8 of coffee-script was just published.

Branch Build failing 🚨
Dependency coffee-script
Current Version 1.12.7
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

coffee-script is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details
  • coverage/coveralls First build on greenkeeper/coffee-script-1.12.8 at 95.294% Details

Commits

The new version differs by 11 commits ahead by 11, behind by 7.

  • 943579a 1.12.8 (#4801)
  • 8bb89d8 Backport #4783, fix for export default followed by an implicit object (#4800)
  • f301b04 [CS1] Add postinstall message for direct installs of ‘coffee-script’ (#4759)
  • c5f4314 [CS1] Travis CI for 1.x (#4797)
  • 1ad9c61 Revise v1 docs to reflect that v2 is out; update paths to reflect that the v2 docs are now the primary docs, and the v1 docs only live under /v1/
  • 249cc59 Remove v2 docs
  • e7073bc Update CS2 docs per #4688
  • 458440e 2.0.0-beta5 docs
  • 6cea181 [CS1] fix #4260 and #1349: splat error with soak properties or expressions (#4643)
  • e3c2c03 2.0.0-beta4 docs
  • 27f21a3 1.12.7 (#4617)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

半角カタカナの取り扱いについて

hiraganizeやkatakanaizeで入力に半角カタカナを使用した場合に、変換後ひらがなやカタカナに変換されないようです。仕様でしょうか?

また、全角カタカナを半角カタカナに変換する関数は存在しないのでしょうか?

お忙しいことと思いますが、お時間の空いた時に回答していただけると幸いです。

An in-range update of gulp-rename is breaking the build 🚨

Version 1.2.3 of gulp-rename was just published.

Branch Build failing 🚨
Dependency gulp-rename
Current Version 1.2.2
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

gulp-rename is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 20 commits.

  • 239c2b6 exclude package-lock
  • 8d4eecc update deps, 1.2.3
  • 165949e Merge pull request #79 from TheDancingCode/remove-gutil
  • 33e3fa7 Update engines field in package.json
  • 8104e4b Update travis build
  • bb11b80 Make test pass on Windows
  • 457db2e Fix code style error
  • bdfc359 Drop dependency on deprecated gulp-util
  • 3b4fdf8 Merge pull request #72 from lleaff/patch-1
  • fa84ece Fix confusing example
  • 17d44ec Merge pull request #56 from Josiah/clone-original-file
  • ba5ab6d Merge pull request #57 from florianeckerstorfer/patch-1
  • 6cf0627 Return path in rename by function example
  • 5001e08 Test that gulp-rename works for parallel streams
  • fb1a8e3 Clone the original file prior to renaming

There are 20 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of gulp-mocha-phantomjs is breaking the build 🚨

Version 0.12.2 of gulp-mocha-phantomjs was just published.

Branch Build failing 🚨
Dependency gulp-mocha-phantomjs
Current Version 0.12.1
Type devDependency

This version is covered by your current version range and after updating it in your project the build failed.

gulp-mocha-phantomjs is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details
  • coverage/coveralls Coverage pending from Coveralls.io Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

An in-range update of big.js is breaking the build 🚨

Version 5.1.0 of big.js was just published.

Branch Build failing 🚨
Dependency big.js
Current Version 5.0.3
Type dependency

This version is covered by your current version range and after updating it in your project the build failed.

big.js is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.

Status Details
  • continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 5 commits.

  • 25f2971 v5.1.0
  • 08ee99c Amend .mjs exports. Remove extension from main field in package.json.
  • 12a9eac Merge pull request #94 from jaeh/master
  • e8066fb Update package.json
  • 8871284 add module and jsnext:main field

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.


Your Greenkeeper Bot 🌴

Option to keep non-Japanese text?

Currently, this

var japanese = require('japanese');

console.log(japanese.romanize('感じ取れたら手を繋ごう、重なるのは人生のライン and レミリア最高!'));
console.log(japanese.romanize('shelah'));

strips out all non-Japanese text (so the 2nd line doesn't output anything). Is it possible to keep the non-Japanese characters?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.