it solves the problem of languages where it doesn't make any sense to have   at all, but translators go "wtf is that" and include it
nikki
isn't there some css stuff for avoiding wrapping anyway?
warp
ianmcorvidae: do you think that would be less of a problem with ? or about the same?
nikki
the latter is clearly a space and won't be included by people who know there's no space. nbsp is clearer in that people have more chance of recognising what it is
ianmcorvidae
less, because people have some idea what nbsp is
warp
(i.e. is it likely that translators do not know html character references at all, or is it likely they don't know the numeric ones but would be familiar with the named ones?)
ianmcorvidae
the latter, though ndash vs 70695238345 or whatever it is benefits more
if it was &nonbreakingspace; or something they'd be comporable
comparable*
warp
ianmcorvidae: would it be possible for the tools which extract strings to perform a translation from &xa0; to ?
ianmcorvidae
it'd be possible, I suppose
warp
ianmcorvidae: and do the reverse transformation in the build step?
ianmcorvidae
I almost feel like that's the wrong place though, it'd be better to just have in our source and have the translation system (whether or not it's actually translating to another language) turn to  
warp
ocharles didn't want to have these transformations applied at runtime, but I think there is value in doing them, and I expect ocharles will be less opposed to doing this at build time.
ianmcorvidae
ah
runtime is a bit iffy, yeah, it makes things nicest for contributors and translators though
warp
yes. I'm trying to find a workable compromise between the two extremes :)
kovacsur joined the channel
ianmcorvidae
understood :)
Freso
My vote'd be for runtime.
ianmcorvidae
honestly, my initial vote is for "do we need the damn things at all?"
warp
(it's a shame HTML5 is so very lenient in many ways yet doesn't allow the bits needed to specify character entities when parsing it as xml)
Freso
Developer-translators occasionally grep for translations string sin the code.
*strings in
If the string is being changed between source and .pot, that won't work.
warp
ianmcorvidae: yes. I like the mdashes and nbsps where we use them correctly.
reosarevok
v6lur, ping
ianmcorvidae remains unconvinced :)
intgr would work too
" which of the two "ja" should become "ning"?
ianmcorvidae
anyway also, to start the task will be making sure we don't lose translations with what we currently have, which is independent of fixing the underlying problem
which hopefully I'll get a chance to do, heh
reosarevok
(taking into account "orchestra and choir" are a package inside the full credit)
ehrgeiz joined the channel
intgr
reosarevok: Doesn't matter, "ja" and "ning" are the same word. You can leave them both "ja".
reosarevok
I thought I was supposed to use one of each when there are several levels in an enumeration
intgr
It wouldn't clarify anything in this context.
v6lur
reosarevok: some would say that ning is a stronger separator, i.e. similarthing1 ja similarthing2 ning differentthing1 ja differentthing2
i.e. Ülle Ulla ning RAT ...
but "ja" for both is ok, too
reosarevok
Hmm, ok
ehrgeiz
> navap: General FYI, according to google webmaster tools, Susumu Hirasawa is the highest ranked artist by number of incomming links from unique domains < He is linked on every WP template page for an muscbrainz artist, guess thats giving him a nice boost
reosarevok
I'll leave ja then
v6lur
reosarevok: re: "use one of each when there are several levels" -- in literary style, you would :)
i'm not sure which style is approppriate for MB
reosarevok
Neither am I :)
v6lur
intgr: it would carify a bit -- namely that the choir is that of the RAT Estonia
(i mean using "Ülle Ulla ning RAT Estonia ork. ja koor" would)
if CallerNo6 reads the chatlogs: IIRC I deleted the Glenn Gould wiki page because every info on it is on the release page. Unfortunately I cannot verify because this release still causes a 502. And it was a box set not a series anyway, so I think this was ok
kurtjx joined the channel
drsaunde joined the channel
reels_ joined the channel
CallerNo6 joined the channel
CallerNo6
MClemo: about the Glen Gould, that makes sense, thanks
I seem to recall there being a weird issue a while ago with locales (and multiple names for the same artist). Was any action ever taken on that, to move everything to a "script" rather than "language"?
Freso
No.
Also, it's not as simple as that, as sometimes you do want a locale.
(locales are not languages.)
belak
Shouldn't there be a way to specify that multiple languages are the same?
hawke_1
You mean, that one name applies for multiple locales?
belak
Yeah
Like, say en_US and en_GB
hawke_1
Would be nice, wouldn’t it?
But no, there’s no way to do that, other than entering it many many many times
belak
Ugh
There has to be a better way...
hawke_1
Not at the moment, no.
nikki
you should only really use en_US and en_GB if the names are specific to those countries
Freso
belak: "en_GB" and "en_US" does denote that the languages are the same.
belak: That's the "en" part.
*do
kepstin-laptop
applications are generally designed such that if a user requests en_GB and only en is available, they'll get en.
ianmcorvidae
we really need to replace our locale system in order to have more control over it
there's a number of issues; we're just using a list from some perl module at present
Freso
Re: what nikki just mentioned, it'd be nice to have a way to target e.g. an alias at a country regardless of language.
(E.g, Wedlock is known as 105 Owl something in the GB/UK, apparently. And while this may seem to map easily to en_GB - what about sco, cy, ga, ...?)
kepstin-laptop wants alias scripts, as well... and thinks he's figured out a way to hack that in.
nikki
I liked freso's mul-latn suggestion
kepstin-laptop
hmm, I think mul-Latn actually fits in with my idea fine.
nikki
what's your idea then? :P
kepstin-laptop
use IETF language tags with the general format en-GB-Latn
country and script are each optional
nikki
that's more or less what we have now
kepstin-laptop
yeah, pretty much just that with a script tag stuck on the end.
(the script tag is optional in the case where it's the same as the language's standard script)
nikki
well, *some* of our entries already have scripts, like chinese
Freso
kepstin-laptop: But what if something applies to one script or one country across different languages?
nikki
the problem is more the interface
kepstin-laptop
freso: I said that I like your mul idea. so mul-GB-Latn and mul-Latn work there :)
nikki
right now we generate a list and it's not that flexible
best thing I can think of for the ui is to allow selecting language, country, script separately.
where country, script would default to "any country" and "language's standard script"
ianmcorvidae
a "commonly used complete locales" interface would be good too
Freso
Yeah, that Freso guy did make a good suggestion there.
kepstin-laptop: +1
kepstin-laptop notes that the IETF tags have a different way to mark traditional vs. simplified chinese writing that doesn't conflate them with cantonese vs. mandarin or whatnot.