Last modified: 2012-10-28 12:12:51 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T30712, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 28712 - Lqt should notify in recipient's language
Lqt should notify in recipient's language
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
LiquidThreads (Other open bugs)
unspecified
All All
: Low normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
https://translatewiki.net/wiki/Thread...
: i18n
Depends on:
Blocks: gender
  Show dependency treegraph
 
Reported: 2011-04-26 23:40 UTC by Purodha Blissenbach
Modified: 2012-10-28 12:12 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Purodha Blissenbach 2011-04-26 23:40:08 UTC
See better formatted description of oddities at
Comment 1 Purodha Blissenbach 2011-04-26 23:42:57 UTC
https://translatewiki.net/wiki/Thread:Support/Odd_language_mix_in_lqt_notification_e-mail_from_translatewiki.net

I have got a notification e-mail about my altered user_talk page on translatewiki.net. It is message lqt-enotif-newthread (in version oldid=2836668 of February, 22th)
Here is a copy of the e-mail body:

Leeven Purodha,
dat hee es en Nohreesch translatewiki.net,
dat ene neue Diskussionsstrang zom Teema
„[[StatusNet:Emailsummary-a06ed6130aa26671389f191e1440733bd0c8f3a4-p a href=" 1s" change your em/en]]“
öm 18:29 Uhr aam 24. Aprel 2011 op dä Sigg User talk:Purodha
dobei jekumme es. Jeschrwevve däd_en dä Metmaacher Giftpflanze

Beloore kanns de dä op
<StatusNet:Emailsummary-a06ed6130aa26671389f191e1440733bd0c8f3a4-p_a_href=_1s_change_your_em/en]]_13018">http://translatewiki.net/w/i.php?title=User_talk:Purodha&offset=20110424182948&lqt_mustshow=13018#[[StatusNet:Emailsummary-a06ed6130aa26671389f191e1440733bd0c8f3a4-p_a_href=_1s_change_your_em/en]]_13018>

Der Täx es:
Hallo Purodha,

du hast das auf /en übersetzt, das sollte wohl aber auf /ksh, oder?

Ene schööne Jrohß!

This e-mail has oddities:

   1. The result of {{int:lqt-history-thread}} is from the wrong language, German (de) instead of Colognian (ksh), or 1st fallback language, not the message language itrself, that is, we read "Diskussionsstrang" (wrong) not "Jeschprääschßfäddem" (right). On the message page, MediaWiki:Lqt-enotif-newthread/ksh, it appears correct, at least when I am viewing it. My user language is ksh.
   2. The result of {{GRAMMAR:Genitiv vun|{{SITENAME}}}} is wrong. There is no article+preposition added, as it should be. This appears correct on the message edit page, and incorrect on the mesage page, which is a known deficiency. In the e-mail, GRAMMAR could be taken from German (de), but there are many other explanations as well.
   3. {{GENDER:$8|dä|dat|dä Metmaacher|de|et}} at least was taken from Colognian (ksh) in the e-mail and appears to be correct.

These oddities are not systematic, though.
Comment 2 Purodha Blissenbach 2011-05-03 13:58:13 UTC
More similar e-mails suggest that the langauge inserts via int: 
and possibly the GRAMMAR: and GENDER: routines are taken from the user language
of the user making the change triggering the e-mail to be sent.

I needed, I can supply screen shots or copies of the e-mails.
Comment 3 Bugmeister Bot 2011-08-19 19:12:16 UTC
Unassigning default assignments. http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/54734
Comment 4 Nemo 2012-07-25 06:50:05 UTC
I would have sworn this was a duplicate, but it seems not.
See also bug 27408 comment 1 (in following comments Niklas mentions the origin of the problem, maybe it's the same here).
Comment 5 Siebrand Mazeland 2012-10-20 23:12:25 UTC
Please let us know if the observations mentioned in comment 2 are still valid. Lqt now uses the Message class, instead of the deprecated wfMsg* methods. I'm hoping this has made things better :).
Comment 6 Siebrand Mazeland 2012-10-28 12:12:51 UTC
Considering this resolved.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links