• S (unregistered) in reply to no laughing matter
    no laughing matter:
    Half the users in Germany have set their language settings to english? WTF?!?

    Quite plausible, actually. Most Germans speak English just fine, and given the use of automated translation, they can probably understand the original English text better than they can understand the machine-translated German...

    I'm not joking, either. I spent some time in Peru some years back, and while my Spanish is almost non-existent, it was generally easier for me to read signs and stuff in Spanish than it was to read the horribly-mangled English translations that were sometimes provided.

  • Norman Diamond (unregistered)

    One time in a previous millennium, a translation of a German article taught me that the three kinds of disk drive interfaces were IDE, OATH, and SCSI.

    Before programs reached that level of expertise, translations were performed by humans. Like the one who informed our customers that file output was cached in correct buffers.

  • QJo (unregistered) in reply to S
    S:
    faoileag:
    Very mysterious. I would have expected the translated javascript statement to be: 
    pour (var i = 1; i < a.longueur; i++) {
    Which adds to the suspicion that everything apart from the obious wtf ("we ran the whole html page through a translater, not only the content, ha, ha, ha, stupid us") is embellishment.

    Or, just as likely, the tool that extract text from the page failed to recognise "length" as a word due to being preceded by a period instead of whitespace.

    Possibly it's been programmed to understand that dot-delimited strings are part of a URL / email address / etc. and therefore should not be translated. Thus neither "a" nor "length" are translated, although "a. length" would indeed be translated to "un. longueur".

    As to why "i" is left untranslated, this is probably because the translation program, sensibly and intelligently, recognises only "I" as the frist person singular nominative personal pronoun.

  • John (unregistered) in reply to Balu
    Balu:
    Trello:
    TRWTF is using a regex for validating emails.
    What do you suggest? (disclaimer: I know most people do email address validation wrong, but email addresses can be validated using regular expressions)

    You can't validate an email address using a [b]regular[b] expression as the email spec says you can have an infinite number of nested balanced < word > constructs.

    You can however use a Perl Regex, which I normally think of as Regular Expressions on Steroids :-)

  • (cs) in reply to me
    me:
    Harrow:
    faoileag:
    Very mysterious. I would have expected the translated javascript statement to be: 
    pour (var i = 1; i < a.longueur; i++) {
    I would have expected: 
    pour (var je = 1; je < un.longueur; je++) {
    Plus un. Cela me fait LOL.
    More commonly, "Cela me fait mdr." (mort/mourir de rire, die/died/etc of laughing)
  • faoileag (unregistered) in reply to Dentricx
    Dentricx:
    faoileag:
    Or you could use google to find some french sites about programming and take the correct translation from one of those sites: "Expressions régulières" seems to be the accepted term (found in http://formation-perl.fr/guide-perl-08.html et al.).
    Have you read your linked site ?
    Of course not. But since you seem to think I should, I did now.
    formation-perl.fr dis:
    ce qui a donné en français une traduction correcte "expressions rationnelles" et une traduction mot à mot "expressions régulières". La seconde est entrée dans les mœurs et sera donc utilisée ici.

    Where's your problem?

  • Nico (unregistered)

    Having customers all over the world: check Having a multiple geographies dev team: check Having a few hundred dollars to pay a proper translator instead of relying on some crap API: fail

    Captcha: damnum - I'll tried calling you but I had the wrong damnum

  • Rudolf (unregistered) in reply to faoileag
    faoileag:
    MerdeMan:
    Try this regex buddy:

    [a-zA-Z0-9._-]+@(?:[a-zA-Z0-9-]+\.)+[a-zA-Z]{2,6}

    Does it choke on IDNs?

    DNS host names can only contain alphanumeric characters and the hyphen (and . to separate parts).

    IDNs use trickery (punycode) to look international.

    In the Wikipedia article the first column is the REAL DNS name - the second column is how an IDN-aware program will display it.

    Really, hardly anyone uses IDNs in real-life - they won't work most places, unless you type in the punycode version, so you're better off getting a Latin-ised version of your domain name, which at least means something wherever you using it, rather than an IDN which has a totally meaningless punycode version.

  • (cs)

    Why not just do the most basic validation (contains the @ symbol, etc), but not "perfect" validation, then attempt to send the email, and if it fails, alert the user? Or even use an existing construct, like the System.Net.Mail.MailAddress class to see if it can be parsed, and let Microsoft worry about it.

  • Gechurch (unregistered) in reply to AndyCanfield
    AndyCanfield:
    Why bother validating e-mail addresses? Your code can, at best, reject "merde" and accept "[email protected]", but there is no user named "merde" on Yahoo. Sending a confirmation message takes a few seconds but validates not only the account format but the account existance also. Lots of sites do this during signup.

    Lots of sites send a confirmation email, but almost all of them combine it with some form of email address validation. The reason is that what you're proposing (confirmation email and no email verification) leads to a poor user experience.

    I sign up but make a simple/common type in my email address (forget the TLD, accidently add a space etc). The site happily accepts it and sends off an email and tells me to check my Inbox. The email doesn't come. I check my junk mail folder and can't see it, so decide to wait ten minutes in case there was some sort of delay. It still doesn't come so I go back to the site and have to complete the entire sign-up form again.

    If you decide to allow any format email address at all that's fine, but at least provide a client-side warning telling the user that their email address looks unusual and they may want to check it for typo's. I'd guess that for every user with a valid email address that has a space, or no TLD or whatever, there are another 99 users that "don't know computers very well" and are making simple typo's.

  • WTF is Yvonne? (unregistered)

    TRWTF is that someone has a name Yvonne. How do you even pronounce it, and why would anyone want such a crappy name?

  • QJo (unregistered) in reply to WTF is Yvonne?
    WTF is Yvonne?:
    TRWTF is that someone has a name Yvonne. How do you even pronounce it, and why would anyone want such a crappy name?

    Popular girl's name in the UK, at least. It's pronounced Ee-von, with the stress on the second syllable.

    Better than your Euniquewa, Taneisha, Lateisha and whatever other stupid made-up gawky-slang that goes for "names" in the glorious US of A.

  • nobulate (unregistered) in reply to Mike
    Mike:
    Shouldn't for "(var i = 1; i < a.length; i++) {"

    come out as

    pour (il est je = 1; je < un.lonueur; je++) {

    Of course, but they got to dumb it down for us readers of TDWTF so we can get the joke.

  • v (unregistered) in reply to Matt Westwood
    Matt Westwood:
    Dentricx:
    DaveK:
    Some programmers, when they think of solving a problem with regular expressions, can't remember the French for 'regular expression'.

    Now they have three problems.

    Especially since the translation of "regular expression" in french is a troll in itself. Some (including me) argue for "expression rationnelle", other argues for "expression régulière" (which sort of translates to "recurring expression").

    "expression norme" or "expression canonique" may be appropriate.

    Although now its etymology has been called into question, I now wonder what's so "regular" about a "regular expression".

    In fact "recurring expression" might turn out to be a quite accurate account of its etymology - from the Kleene operator "*" used in formally defining what a regular language means as well as in the regular expression syntax itself to indicate any number of repetitions.

  • (cs) in reply to QJo
    QJo:
    WTF is Yvonne?:
    TRWTF is that someone has a name Yvonne. How do you even pronounce it, and why would anyone want such a crappy name?

    Popular girl's name in the UK, at least. It's pronounced Ee-von, with the stress on the second syllable.

    Better than your Euniquewa, Taneisha, Lateisha and whatever other stupid made-up gawky-slang that goes for "names" in the glorious US of A.

    Those are African American names, Yvonne is generally a Latin name. I do have a friend named Yvonne, it should not come as a surprise that she lives in Miami.

  • Neil (unregistered) in reply to Matthias
    Matthias:
    In Outlook the "Re:" prefix in E-Mails was translated to "AW:", so conversations across countries led to subject lines like

    Hello! Re: AW: Hello! Re: AW: Re: AW: Hello! Re: AW: Re: AW: Re: AW: Hello! Re: AW: Re: AW: Re: AW: Re: AW: Hello! Re: AW: Re: AW: Re: AW: Re: AW: Re: AW: Hello! Re: AW: Re: AW: Re: AW: Re: AW: Re: AW: Re: AW: Hello!

    If, as a Thunderbird or SeaMonkey user, you receive replies with, say, an AW: prefix, you can set the about:config editor mailnews.localizedRe preference appropriately to stop yourself quoting the AW: prefix on your reply. Note: the setting does not take effect retroactively, but you can destructively rebuild the folder summary file if you insist.

    If you use one of the localised versions below then the prefix(es) will have been preconfigured for you, but you can still alter the setting. Беларуская (Belarus): Адказ Dansk (Danish): SV Deutsch (German): AW,Aw (strangely SeaMonkey also accepts Antw:) Eesti keel (Estonian): Vs Euskara (Basque): er Suomi (Finnish): VS, SV (SeaMonkey only accepts VS:) השב (Hebrew): עברית Magyar (Hungarian): Aw,SV,Vá Íslenska (Icelandic): SV Lietuvių (Lithuanian): Ats. (also in SeaMonkey) Norse Bokmål (Norwegian): SV (also in SeaMonkey) Norse Nynorsk (Norwegian): SV Polski (Polish): Re,RE,re,rE,Odp,Odp.,ODP (SeaMonkey does not accept Odp.:) Português do Brasil (Brazilian Portugese): RES (Res: in SeaMonkey; yes, it's case-sensitive) Shqip (Albanian): Për Svenska (Swedish): SV (also in SeaMonkey) Türkçe (Turkish): YNT,Yan

  • meagain (unregistered)

    Why was she working late hours in New York if the developer was in France? They would stop working in France 5 hours before than in New York. How frequent is the lemma pour in any language? This entire article smells of bullshit.

  • (nodebb)

    thanks for info

  • (nodebb)

    really cool

    Addendum 2022-11-20 20:56: To be honest, it's quite challenging for me because my friend lives in yoruba. Here are several of the misunderstandings that arise while translate yoruba . I became convinced that a good translation is essential in this situation because a language barrier frequently prevents people from forming connections.

  • Jimmyanten (unregistered)
    Comment held for moderation.

Leave a comment on “Translate Everything!”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article