4 ms·

The contexts remains ReadMe files on Github. Remember that. If you wish to write a program to do Y then write the code your tests etc using whatever encoding m

The contexts remains ReadMe files on Github. Remember that. If you wish to write a program to do Y then write the code your tests etc using whatever encoding makes you happy. Nowhere have I said no Unicodein any repositories which is the strawman you are reachinging for. You can still write Readme files without Unicode so that the great majority of user of public Github can see what your project is about. Now there are many close editors today that do not support full unicode Presumably advocating unicode should not discriminate against languages with Arabic. Most code editors can not do that right out of the box. More and more can.

detaro 6y ago
> the great majority of use The great majority of users has editors that can handle unicode. What editor common today doesn't do UTF-8?
gostsamo 6y ago
Let's imagine that I'm writing a cyrillic program. The users are most likely not english, the stakeholders are not english, the examples that the program works with are not ascii. Yet, you insist that in the readme I'm not using anything cyrillic related and use ascii instead. If I happen to find an arabic readme, then I'll know that either I'm not the target audience, or that the author does not know english and might loose my contributions. Neither of those gives me the right to open a PR and insist that the readme is adjusted for my use case only and degrades the user experience of others. What I strongly disagree with you is that from the principal of "be conservative in what you send and liberal in what you accept" you choose to take only the first part and forget the latter. Ascii is nice when it is applicable for the use case, but it is not universally applicable and assuming so should be a personal mistake, not tax on everyone. Maybe the disagreement between us is in how we define target audience. You imagine that if it is published in Github, then it must be readable to anyone there. I think that if the project is ment to help certain type of people, then it it must be optimized for them, not for people who would never bother using it anyways.

detaro 6y ago

> the great majority of use The great majority of users has editors that can handle unicode. What editor common today doesn't do UTF-8?

gostsamo 6y ago

Let's imagine that I'm writing a cyrillic program. The users are most likely not english, the stakeholders are not english, the examples that the program works with are not ascii. Yet, you insist that in the readme I'm not using anything cyrillic related and use ascii instead. If I happen to find an arabic readme, then I'll know that either I'm not the target audience, or that the author does not know english and might loose my contributions. Neither of those gives me the right to open a PR and insist that the readme is adjusted for my use case only and degrades the user experience of others. What I strongly disagree with you is that from the principal of "be conservative in what you send and liberal in what you accept" you choose to take only the first part and forget the latter. Ascii is nice when it is applicable for the use case, but it is not universally applicable and assuming so should be a personal mistake, not tax on everyone. Maybe the disagreement between us is in how we define target audience. You imagine that if it is published in Github, then it must be readable to anyone there. I think that if the project is ment to help certain type of people, then it it must be optimized for them, not for people who would never bother using it anyways.