Leave a comment

Re: To me, "unspecified" is offensive azurelunatic January 31 2010, 08:48:38 UTC
As I understand how this thing works, "unspecified" is what it's called in the guts of the programming, but through the magic of the translation system (and I have been assured that the kind of magic that involves the translation system is cthonic), the "unspecified" variable can be displayed labeled as anything that the people with access to the translation system like.

It looks like someone reasonably quick-thinking with access to update en_LJ has arrived on the scene, because one of my compatriots in IM just pointed me at http://www.livejournal.com/translate/diff.bml?lang=en_LJ&it=1:6084&change=3 which is a distinct change for the better, and I thank them for it. Whoever they are. ♥

Reply

Re: To me, "unspecified" is offensive elionwyr January 31 2010, 08:52:43 UTC
Thank you for that linkage..much better, though I'm full of curiosity as to the history of this decision to change and rechange.

Still, thankee!

Reply

Re: To me, "unspecified" is offensive pauamma January 31 2010, 19:41:05 UTC
Thanks for pointing this out, BTW. For some reason, the "original English" text still displayed the "it's personal" version when I went in to update the French translation, so I likely wouldn't have noticed for a while otherwise.

Reply

Re: To me, "unspecified" is offensive azurelunatic January 31 2010, 23:15:45 UTC
Dre says it's heavily, heavily, heavily cached.

For the purposes of the translation system, I think that should be considered a bug and a change proposed.

Reply

en(_LJ) string update lag pauamma February 1 2010, 16:33:12 UTC
There may be one already, but I don't have access to Jira ATM, so can't check. If there isn't: this is probably the same problem as http://bugs.dwscoalition.org/show_bug.cgi?id=405 (which will eventually be fixed by applying high explosive to the whole translation system, which is one of the reasons we didn't try very hard to patch that particular problem).

Reply

Re: en(_LJ) string update lag azurelunatic February 1 2010, 18:39:21 UTC
No such bug in volunteer-accessible side of Jira at the moment.

Looking at the above bug, I wonder if the reason DW isn't experiencing it, and the reason that, over 24 hours since the ever-loving string has been changed, I am still seeing the version with the for-the-love-of-pete "smart" quote, is because of a scaling problem.

I've lodged http://www.livejournal.com/support/see_request.bml?id=1044083 in Docs; at the time I put that in there, the lag was still within the realm of reasonable for the whole site. It's now approaching 48 hours, and I'm just shy of running around in circles in IRC shouting GET IT OUT GET IT OUT GET IT OUT, which differs from Saturday in that I'm doing this in main-channel rather than a side channel.

Reply

Re: en(_LJ) string update lag pauamma February 1 2010, 19:09:39 UTC
Thanks for the link. When you file that bug, can you put me on the cc: list?

Reply

Re: en(_LJ) string update lag azurelunatic February 18 2010, 23:36:59 UTC
Jira (or, rather, at least my access to same) doesn't appear to allow me to do that, but other considerations permitting, I will keep you in the loop in your capacity as translator.

Reply

(The comment has been removed)

Re: To me, "unspecified" is offensive azurelunatic February 1 2010, 19:39:04 UTC
Though it's more than 24 (going on 48, as the 32 mark has been passed) hours later, and the version with the "smart" apostrophe is still visible on my profile.

This is actually not pleasing me very much, but at least it's the "eww it's a bug" sort of "not pleasing", with a side serving of "GET IT OFF ME GET IT OFF ME".

Since apparently en_LJ strings aren't updated that often (aveleh says that generally new ones are created if there's something new on the site) there's very little poking that's been done into "hmm, that's weird" behavior for this.

Reply

Re: To me, "unspecified" is offensive trixieleitz February 1 2010, 05:12:36 UTC
Oh, phew!

Reply


Leave a comment

Up