Title



  • 0_1482889719980_Bez tytułu.png

    Snarky comment



  • And when I click "Anuluj"...

    0_1482889907433_Bez tytułu.png

    Not only they can't print non-ASCII characters, but also the right button label goes out of bounds. Has it ever been tested by anyone!?

    Edit: I just noticed some characters are printed correctly. Not sure if it's better or worse...

    Edit 2: from what I see, it's not about non-ASCII characters - it's about non-ASCII characters at the end of the words. The ones in the middle are fine, and ones at the end also remove the space. As if the character and the space were interpreted as single code point, and then proclaimed invalid. I don't even want to know how they did it.



  • 0_1482905623052_upload-f48976d6-b156-4bdd-b23d-a94b1d9a710b


  • sockdevs

    Terrible attempt at a joke


  • Discourse touched me in a no-no place

    @Gąska said in Title:

    Edit 2: from what I see, it's not about non-ASCII characters - it's about non-ASCII characters at the end of the words. The ones in the middle are fine, and ones at the end also remove the space. As if the character and the space were interpreted as single code point, and then proclaimed invalid. I don't even want to know how they did it.

    It's like they're feeding each word in one by one and somehow mangling the detection of the word boundaries, or maybe failing at understanding the difference between words and characters and so feeding in a slightly short string in some cases…

    No, I think I don't want to know any more either.



  • @RaceProUK said in Title:

    Terrible attempt at a joke

    Inevitable reminder that terrible jokes need more :rimshot:



  • @Gąska said in Title:

    Has it ever been tested by anyone!?

    Do you really need to ask that?



  • @anonymous234 I can totally see it being thoroughly tested, the bugs were reported, and the management said "fuck this shit, we can't put another 10 man-hours into it", and tickets were closed as wontfix.


  • area_pol

    @Gąska said in Title:

    @anonymous234 I can totally see it being thoroughly tested, the bugs were reported, and the management said "fuck this shit, we can't put another 10 man-hours into it", and tickets were closed as wontfix.

    Tickets were closed as fixed. Wontfix looks bad on quarterly reports.



  • @Gąska said in Title:

    I can totally see it being thoroughly tested

    A US company thoroughly testing with non-ASCII characters? :rofl:

    TBH, even my own scripts that I have written specifically to process non-ASCII text I don't thoroughly test. (What encoding is that string I copied from $random_web_page whose encoding may or may not be correctly described in the page's headers and pasted via the Windows clipboard? Now that I've guessed, use it to create both UTF-8 file content and an almost-but-not-quite-UTF-16 Windows file name.)



  • @HardwareGeek said in Title:

    @Gąska said in Title:

    I can totally see it being thoroughly tested

    A US company thoroughly testing with non-ASCII characters? :rofl:

    It's not even that. They already made the effort to translate the whole thing - and it looks like no one even checked if it's working at all. I'd think at least the person doing the translation would want to take a look at their work.



  • @Rhywden Whaargarbl!





  • @Gąska said in Title:

    I'd think at least the person doing the translation would want to take a look at their work.

    I suspect most software translators don’t get to see the finished product unless it happens to be something they use themselves for whatever reason. Even then it’s (hopefully) unlikely they’ll see error messages they helped translate.



  • @Gąska said in Title:

    I'd think at least the person doing the translation would want to take a look at their work.

    :rofl: I know our translators don't see the end result. Months later we'll get a bug report from QA that the text doesn't fit.



  • @dcon said in Title:

    @Gąska said in Title:

    I'd think at least the person doing the translation would want to take a look at their work.

    :rofl: I know our translators don't see the end result. Months later we'll get a bug report from QAthe customer that the text doesn't fit.

    FTFY



  • @djls45 That too. It's a 50/50 crap shoot.



  • @Gąska Even at Microsoft, the translators sometimes do not even know where the translated text will appear, let alone test that it is appropriate there...

    Proof from Word 2010

    For those that don't understand German: The icon depicts a "vertical scroll" ("scroll" being a noun referring to an ancient roll of material to be written onto) but the tooltip translation means "scroll vertically" ("scroll" being a verb referring to the action of moving the screen content).



  • @mihi yeah, I remember seeing a calculator program translated to Polish which had "OCT" and "DEC" buttons translated to respective months.



  • @mihi Ah yes, the confusion between nouns and verbs in software translated from English is ubiquitous.

    Another favorite of mine is confusing "play" as in play a movie and "play" as in play a game, which in most languages are not the same verb.



  • @anonymous234 said in Title:

    @mihi Ah yes, the confusion between nouns and verbs in software translated from English is ubiquitous.

    I wouldn't be surprised if it was often because the original programmer reused the dictionary entry for both and there was literally no way for translations to work around that.



  • @djls45 said in Title:

    @dcon said in Title:

    @Gąska said in Title:

    I'd think at least the person doing the translation would want to take a look at their work.

    :rofl: I know our translators don't see the end result. Months later we'll get a bug report from QAthe customer that the text doesn't fit.

    FTFY

    But QA is the customer...


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.