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.

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

Explain the name of the repo in the README #102

Open
curquiza opened this issue May 18, 2022 · 3 comments
Open

Explain the name of the repo in the README #102

curquiza opened this issue May 18, 2022 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation

Comments

@curquiza
Copy link
Member

curquiza commented May 18, 2022

Following the @CaroFG idea, we could explain the name of the repo in the README since some people finds it "offensive"

Here are some explanations Many made on Twitter:

we choose the name of this repository in the same mood as discord or meili, giving the name of the problem we want to solve.
Personally, I don’t feel like it’s an offensive word, but more a funny pun with “char”.
Moreover, other tokenizers don’t always have an understandable name, for instance lindera maintained by @minoru_osuka or even jieba.
I hope my explanation was clear enough and I hope the name will not discourage you to use or even contribute to the project! 😊

@curquiza curquiza added documentation Improvements or additions to documentation good first issue Good for newcomers labels May 18, 2022
@Mount-Blanc
Copy link

Hello, I would like to work on this issue.

@curquiza
Copy link
Member Author

Hello @Mount-Blanc
Thanks for beefing volunteer! 😊
You can open a PR, we will review it asap
I would add something I forgot on the issue description: we called it charabia also because it starts with "char" 😇

@curquiza curquiza removed the good first issue Good for newcomers label Jun 1, 2022
@curquiza
Copy link
Member Author

curquiza commented Jun 1, 2022

Following: #104 (comment)
This is something we would rather not let to the community finally, @CaroFG is indeed the internal Meili people responsible for fixing this issue in the best way!
Sorry again for the confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants