AjaxLife – Request for Translations (also a minor change)

[19:17 06/01/08] I have a Hebrew translation, courtesy of Smiley Barry. I’m waiting on more contributions before I add it in, since doing so involves deploying server code, which is tedious.

[UPDATE 09:39 06/01/08] Fixed a display bug in Firefox, the only browser that actually seems to care about such things, caused by uploading ui.css as text/javascript instead of text/css.

First, AjaxLife now uses javascript files minified and munged by the YUI compressor, then merged into a single file.

Right. Now, it would be very much appreciated if anyone capable of doing so with free time could translate AjaxLife into the language of their choosing, or update the existing translation for that language.

The language file can be found at http://static.ajaxlife.net/translate.txt – to translate it, change the text on the right, in quotes, to the translation of whatever is in it right now. The text outside these quotes must remain unchanged. Additionally, the UI assumes that the strings in some places (e.g. map buttons) will not gain in length significantly – otherwise, the buttons will overlap. Any text in the format #{word} is a placeholder – do not change this text, but place it where the text should go. The word is usually fairly self-explanatory. Please send your files to katharine@katharineberry.co.uk using UTF-8 encoding.

If you know what you’re doing, and there’s already a partial translation for your language, you can find it at http://lab.katharineberry.co.uk/ajaxlife/AjaxLife.Strings.js

Any efforts will be much appreciated.

24 Responses to “AjaxLife – Request for Translations (also a minor change)”


  1. 1 Alister

    Any chance of this change being rolled back? On Firefox the UI is horribly broken – all the buttons appear in a separate frame, crashed together at the bottom of the screen with the minimap just under them – and everything’s gone Times New Roman :( It’s still usable in terms of functionality but it looks extremely weird :O


    Alister

  2. 2 John Drinkwater

    “the only browser that actually seems to care about such things, caused by uploading ui.css as text/javascript instead of text/css.”

    That would be Firefox trying to improve the internet – encouraging correct mime types etc. They call it tech evangelism ;)

  3. 3 Katharine Berry

    Indeed – now, any chance of it also getting upset about leaving a trailing comma at the end of an array?

    I have no objection to this, since it’s a fairly obvious error caused by me leaving text/javascript in the uploader. :P

    It’s also nice to know that I could make a file called blah.thingy, send it as the right mimetype, and have it not get confused. Unlike IE, which invariably does so anyway. >.>

  4. 4 xionbuny

    i keep getting login responce errors, so i cant even log in.

  5. 5 Katharine Berry

    Can’t help you there. I blame LL for having XML forming issues. Or something.

  6. 6 John Drinkwater

    Not sure anything can be done this side of ECMAScript 4 about that… (it should allow trailing commas)

  7. 7 Katharine Berry

    Without having actually taken the time to go and read the specification, I would guess that a trailing comma should imply a null element at the end.

    If you can get IE, Safari and Firefox to all agree on how to render a page, how to deal with trailing commas, and whether or not content-type matters when I’ve quite clearly specified it’s supposed to be treated as a stylesheet of type text/css (I’d say no trailing commas, Content-Type should matter, and there should be no “type” attribute of the <link> and <script> tags in the first place). I take it you take an interest in web standards. :P

    Anyway, this is all off-topic. This is supposed to be about translations! :P

  8. 8 John Drinkwater

    afaik, the issue about an implied null is still unresolved, but I believe it will be taken as a missing element. Trailing commas are mostly accidental, so shouldn’t increase array length (which a null would)

    from wiki.ecmascript.org ;)
    # [OBJECT.TRAILING.COMMA] Allow a trailing comma in an object initialiser.
    # [MSIE.TRAILING.COMMA] Add prose to the spec to clarify that [a,b,c,].length == 3, not 4.
    and well, yeah, I read an insane amount on web standards, without putting it to good purpose…

    Oh, yeah, translations… I can’t provide anything, but: I have a question, are many Brits on the teen grid? Are any of them bothered by lack of en-gb as a language option? Does color and meter not vex you?

  9. 9 Katharine Berry

    It annoys me, but I just ignore it. One could just go through the XUI files and do a search/replace on all these words – being careful not to change the name of anything, which would just break it. Hmm…

    Anyway. It annoys me far more when people use the words in chat. :P

    And what’s with the dots between the words? >.>

  10. 10 John Drinkwater

    Well, I created an en-gb translation a while back (it’ll be outdated now), it’s in the JIRA bug system, but no Brits seem to bother Linden about it, so they don’t know of the need :) Plus, the way SL does translation, ugh, one big ugly mess. Been waiting on their new skin engine they talked about at the last i18n meeting :(

    As for the ’ and … characters, they’re a unicode apostrophe (‘) and ellipsis (…), but done correctly ;) I’m soo used to typing them, I forget some people aren’t utf-8 happy yet. soz :D

  11. 11 Katharine Berry

    I didn’t mean them, I meant “# [OBJECT.TRAILING.COMMA]”

    To be honest, I’m perfectly content with WordPress’ attempts at fixing ellipses and apostrophes… even if it’s using the wrong ones.

    :P

  12. 12 John Drinkwater

    Oh, that’s a bullet point that I copy/pasted from Firefox :P

  13. 13 xionbuny

    i think its cause routers arent supported that i cannot connect :P

  14. 14 Katharine Berry

    If the error message is something to the effect of “Error retrieving login response from server”, it’s actually because of some combination of SL, LibSL, and your account. It’s a highly persistent bug. >.>

  15. 15 xionbunny

    that’s the verry error, well damn cause i really wanna use this :3

  16. 16 xionbunny

    is there any way around it, do i just keep trying to log in or give up XD?

  17. 17 Katharine Berry

    Repeatedly trying won’t help. It used to be an inventory-related issue, caused by certain folder names. However, I only know of one person who ever successfully fixed this, by removing a folder called “1″.

    Sorry I can’t be of more assistance – my only other suggestion is “try another account”

  18. 18 xionbunny

    well i do have a big inventory list and my buddy’s suggestion was to try using an alt as well to have sl switch the asset servers by doing so when logging in apparently, heh.

  19. 19 xionbunny

    i fixed it by deleting all my numbered folders

  20. 20 John Drinkwater

    Sounds like libSL needs a new bug filed?

  21. 21 Katharine Berry

    I don’t have a clue why it’s still happening – the latest version of AjaxLife explicitly does not request the inventory. So why your inventory would still break things is beyond me.

    More debugging is clearly needed.

  22. 22 xionbunny

    keep up the great work :3

  23. 23 Alister

    I think it’s all crashed again…And it hasn’t restarted itself :O

  24. 24 Aurelio A. Heckert

    Translation to Brazilian Portuguese:
    http://www.colivre.coop.br/Aurium/AjaxLifeStringsPtBr
    ;-)

Leave a Reply