4 ms·

> Also, can we please, please, please keep source code files as pure ascii? Asking as a non-native english speaker. I'm a non native English speaker. That's wh

> Also, can we please, please, please keep source code files as pure ascii? Asking as a non-native english speaker. I'm a non native English speaker. That's why I hate tools, and websites which don't understand that people have different letters in names. Just use good tools.

kiriakasis 9y ago
I agree that tools should be better, but i believe that "just use good tools" might not be a viable solution for the parent.
- pleasecalllater 9y ago
  No, there is no justification for bad tools. If someone makes a tool only for ASCII, fine, but don't expect that people will say it's a good tool. Even huge sites have problems when I want to use my real name, or the name of the city I live in. They are usually made by US companies, which is strange, as you have all kinds of people there, with different names. Unfortunately the reality is that those US companies don't care about supporting normal characters people use. Even websites like Upwork don't allow me to enter my real name. Isn't that strange? I have told them about that months ago, nobody cares. So getting to the real problem: supporting unicode is not as hard as it seems, just use from the beginning.
  - setr 9y ago
    >supporting unicode is not as hard as it seems, just use from the beginning. Retrofitting unicode support onto existing programs however is a hard problem for all unicode-lacking but otherwise well-developed tools, with no sufficiently useful and also unicode supporting alternive, that you'd like to use, whats your proposal? Go back in time and tell them to use unicode from the start? Reimpliment them yourself? Give up and say no useful tool for me? There are a hundred reasons certain tooling isn't viable for your usecase; unicode support is rarely even close to being an immediate dealbreaker. Particularly because it can be sufficiently worked around.
jcelerier 9y ago
I'm also non native english and I would much rather have people focus on fixing bugs rather than submitting idiotic translations. Exhibit A: latest GCC error message, "le déréférencement d'un pointeur transtypé à la barbare va enfreindre la règle selon laquelle une zone mémoire ne peut être accédée que par un seul pointeur". Nowadays I just set LC_ALL=C on my machines since translations are so bad.
- Grue3 9y ago
  Just today I was trying to install a new version of Postgres on Windows. For some reason they decided to detect system language and print all error messages in Russian... in the wrong encoding, so it looked like lorem ipsum written in Wingdings font. Took me ages to understand what the problem is. Just use English for god's sake.
  - tutanchamun 9y ago
    Yeah, as a non native speaker I can't agree more. It also makes it easier to find a solution for a problem if all users get the same error message.

kiriakasis 9y ago

I agree that tools should be better, but i believe that "just use good tools" might not be a viable solution for the parent.

pleasecalllater 9y ago
No, there is no justification for bad tools. If someone makes a tool only for ASCII, fine, but don't expect that people will say it's a good tool. Even huge sites have problems when I want to use my real name, or the name of the city I live in. They are usually made by US companies, which is strange, as you have all kinds of people there, with different names. Unfortunately the reality is that those US companies don't care about supporting normal characters people use. Even websites like Upwork don't allow me to enter my real name. Isn't that strange? I have told them about that months ago, nobody cares. So getting to the real problem: supporting unicode is not as hard as it seems, just use from the beginning.
- setr 9y ago
  >supporting unicode is not as hard as it seems, just use from the beginning. Retrofitting unicode support onto existing programs however is a hard problem for all unicode-lacking but otherwise well-developed tools, with no sufficiently useful and also unicode supporting alternive, that you'd like to use, whats your proposal? Go back in time and tell them to use unicode from the start? Reimpliment them yourself? Give up and say no useful tool for me? There are a hundred reasons certain tooling isn't viable for your usecase; unicode support is rarely even close to being an immediate dealbreaker. Particularly because it can be sufficiently worked around.

jcelerier 9y ago

I'm also non native english and I would much rather have people focus on fixing bugs rather than submitting idiotic translations. Exhibit A: latest GCC error message, "le déréférencement d'un pointeur transtypé à la barbare va enfreindre la règle selon laquelle une zone mémoire ne peut être accédée que par un seul pointeur". Nowadays I just set LC_ALL=C on my machines since translations are so bad.

Grue3 9y ago
Just today I was trying to install a new version of Postgres on Windows. For some reason they decided to detect system language and print all error messages in Russian... in the wrong encoding, so it looked like lorem ipsum written in Wingdings font. Took me ages to understand what the problem is. Just use English for god's sake.
- tutanchamun 9y ago
  Yeah, as a non native speaker I can't agree more. It also makes it easier to find a solution for a problem if all users get the same error message.