Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Other textual codes #113

Open
Crissov opened this issue Dec 12, 2017 · 4 comments
Open

Other textual codes #113

Crissov opened this issue Dec 12, 2017 · 4 comments

Comments

@Crissov
Copy link
Contributor

Crissov commented Dec 12, 2017

Some instant messenging apps, e.g. Viber ((foo)) and WeChat/QQ (/:foo and [Foo]), are using various codes to transmit (standard and custom) emojis. Should they be added to the JSON file?
@iamcal
Copy link
Owner

iamcal commented Dec 12, 2017 •
edited
Loading

maybe! depends if there's a data source i can include, or if someone has manually built a mapping

@Crissov
Copy link
Contributor Author

Crissov commented Dec 12, 2017 •
edited
Loading

I could provide some mapping tables: certainly Viber and WAP, perhaps Skype, WeChat, Cisco etc.

Which format would be ideal?

@iamcal
Copy link
Owner

iamcal commented Dec 20, 2017

something similar to data_softbank_map.txt, showing the emoji CP and the representation (using comments in the same way). then the build script can process them

@Crissov
Copy link
Contributor Author

Crissov commented Dec 20, 2017 •
edited
Loading

Understood: # for line comments and fields separated by a space. Other data_*.txt files have fields separated by a semicolon ; or tab.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@iamcal @Crissov