Closed wking closed 9 years ago
On 2015-02-19 12:03 AM, W. Trevor King wrote:
Local names makes sense to me, but I'm not clear on why we should avoid the local character set (e.g. Cyrillic, kanji, etc.). Because almost every scientist can read things written in the Latin alphabet (or some close to it), but most of us can't read other alphabets.
On Thu, Feb 19, 2015 at 02:35:12AM -0800, Greg Wilson wrote:
2015-02-19 12:03 AM, W. Trevor King:
Local names makes sense to me, but I'm not clear on why we should avoid the local character set (e.g. Cyrillic, kanji, etc.).
Because almost every scientist can read things written in the Latin alphabet (or some close to it), but most of us can't read other alphabets.
If the workshop isn't in a language you speak, do you need to read the name? For the odd times that you do need a pronounceable name, you can always paste the native form into a translation service. I'm also fine restricting the slug to ASCII, and having non-native-readers refer to the event by its slug.
Slug in ASCII + title on Software Carpentry website in extended Latin == workable compromise?
On Thu, Feb 19, 2015 at 09:34:28AM -0800, Greg Wilson wrote:
Slug in ASCII + title on Software Carpentry website in extended Latin == workable compromise?
“title on Software Carpentry website in extended Latin” sounds like your starting position ;). I'd rather “Slug in ASCII + title on Software Carpentry website in the event-native language and charset”. I don't think we need to enforce this policy in amy though, I'm happy leaving the title charset up to the admins and convention. That would let us experiment with both approaches and see which was more popular.
At my university we have a special resolution (you can run it through Google Translator if you want) that says "in English you should call this university: AGH University of Science and Technology (abbreviation: AGH UST)".
In Poland we do keep English names when setting up workshop repositories. I think that, at least in Poland, we don't have problems with using only English names of universities for two reasons:
I would not force you to use Polish name of my university ("Akademia Górniczo-Hutnicza im. Stanisława Staszica w Krakowie") and I know people from other Polish universities feel similar. I encourage using English names.
I'm making a call on this one for Version 1: Latin-like names (i.e., Latin characters, possibly accented) for site names, in whatever language the host chooses (so either Uniwersytet w Białymstoku or University of Bialystok). Ditto for personal names and everything else, and we'll revisit after CSV upload is working and this is in production.
Spun off from #188, so it doesn't distract from the search for other documentation.
On Wed, Feb 18, 2015 at 09:16:16AM -0800, Greg Wilson wrote:
Local names makes sense to me, but I'm not clear on why we should avoid the local character set (e.g. Cyrillic, kanji, etc.). It makes sense to me to just go completely native. I wouldn't restrict this to locations either. I don't see why people can't use their native character set for their personal names, or for site names, etc. Python 3 won't have a problem with the Unicode data, and it's easy for users to install a free font (like DejaVu or Unifont) if they are missing the non-Latin glyphs.
Previous discussion on
amy@
:On Tue, Feb 17, 2015 at 10:08:27PM -0800, W. Trevor King wrote:
So: