>
> Also, did you think of the accessibility issues in your solution?
First, I want to clarify that the prototype was made just to communicate
the idea in terms of interaction. The The implementation is just a quick
hack to simulate this interaction.
For a production implementation I can image the whole list of languages to
be sent to the client, and then, the list being shortened by Javascript.
For those users without Javascript (from screen-readers, to Search engine
crawlers) the same list of links they receive now will be available for
them.
In any case, developers could provide even better strategies to solve that.
As an interaction designer I just wanted to share the idea to collect
possible concerns with the interaction proposed, to be fixed in next
iterations of the designs before development effort is made.
On Sat, Apr 20, 2013 at 2:04 AM, Mathieu Stumpf <
psychoslave(a)culture-libre.org> wrote:
> Also, did you think of the accessibility issues in your solution? Here I
> especialy think of people with view disabilities, for who js often mean
> no way to get the content, while a long list of hyperlinks is
> manageable.
>
> Le vendredi 19 avril 2013 à 20:19 +0200, Pau Giner a écrit :
> > Thanks for all the feedback!
> >
> >
> > I'll try to respond below to some of the issues raised:
> >
> >
> > Which is the problem?
> >
> >
> > As it has been mentioned, one of the most effective ways of hiding
> > something is to surround it in the middle of a long list. This
> > produces two problems:
> > * Lack of discoverability. users may be not aware that the
> > content is available in their language (which goes against our
> > goal of providing access to knowledge). Speakers of small
> > languages that access the English Wikipedia because it has
> > more content, are forced to make an effort each time to check
> > if each article is also available in their language.
> > * Problems for multi-lingual exploration. It is hard to switch
> > between multiple language versions since the users has to look
> > for his languages each time in the whole list.
> >
> >
> > The fact that some Wikipedias adjust the order of the languages, the
> > existence of user scripts and an Opera extension to solve the issue,
> > is an indicator of the existence of such problem.
> >
> >
> >
> > We support lots of languages (+300) but users are normally interested
> > in a small (1-8) subset of those. We need to make these subset easily
> > discoverable for our users, and providing them in the middle of a list
> > with 200 items is not the best way to do it in my opinion.
> >
> >
> > Possible cultural and value problems
> >
> >
> > As it was commented, the multilingual nature of Wikipedia is a strong
> > held value. However, currently it is hard to know in how many
> > languages an article is available since you need to count the links.
> > With the proposed approach we provide a number which helps to
> > communicate that. So I think we are not going against that value.
> >
> >
> > I think that concerns about the imposition of languages per region are
> > not a big issue when the previous user choices and the browser accept
> > language are considered with more priority than Geo-IP. Users just
> > need to select their language once and it will be appearing in the
> > short list the next times. These concerns should be more relevant with
> > the current situation where some Wikis put some languages on top
> > regardless user choices (for some work 100% of the time, for others
> > they fail 100% of the time).
> >
> >
> >
> > I also don't think that we should prioritise the need to hide
> > "languages that users somehow dislikes" over making it easy to access
> > the languages that the user wants. In any case, the former is also not
> > supported with the current approach.
> >
> >
> > Why to hide?
> >
> >
> > I understand the problems commented when language links were initially
> > hidden in Vector, since uses were required to make an additional step
> > to get into the same long list of links we currently have. With the
> > proposed approach, the extra step is only taken in exceptional cases
> > (e.g., a user in a foreign country accessing from a public pc), and
> > this is made only once (not for each language change), and aids such
> > as search are provided to make it really quick.
> >
> >
> > The reordering alternative has some problems compared with the
> > proposed approach. For example, when a language does not appear on
> > top, it is hard to determine whether the current article is not
> > provided in that language or it is in the middle of the list. In
> > addition, with reordering, you cannot rely on alphabetical order
> > (while you can present the short list alphabetically).
> >
> >
> >
> >
> > Considering size and quality of the article
> >
> >
> > It can be a factor to consider since communicating that an article has
> > good versions in other languages is a good thing. But I think it is a
> > low priority one, since I find hard to imagine a user selecting a
> > language which she does not understand (otherwise will be already in
> > the short list) just because the article is of good quality. In any
> > case, users normally speak 1-8 languages, so even in a relatively
> > short list there is still room for other criteria.
> >
> >
> > The way to access more
> >
> >
> > We choose the "..." so that the label could work across languages. So
> > that you can go back to your language if you arrive by accident to a
> > foreign Wikipedia (or you are an advanced user curious to check if web
> > fonts were enabled in Javanese wikipedia). However, the visual
> > execution needs some work still to make it more touch friendly among
> > other things.
> >
> >
> > Details on the language list UI
> >
> >
> > The interactive prototype was created to communicate the main idea and
> > most details are still lacking.
> >
> >
> > Thanks for pointing layout and navigation problems. The layout of the
> > list is one of the aspects that needs more work: currently we group
> > the languages by script to help the user to recognise their familiar
> > scripts, and the algorithm also makes some control of orphan/widow
> > items. That works well for very long lists of languages, but needs
> > further tuning when the number of elements is reduced. An algorithm
> > that presents the list optimally for all possible lengths is something
> > to be done.
> >
> >
> >
> >
> >
> >
> > Pau
> >
> >
> > --
> > Pau Giner
> > Interaction Designer
> > Wikimedia Foundation
> >
> >
> > On Thu, Apr 18, 2013 at 6:50 PM, Pau Giner <pginer(a)wikimedia.org>
> > wrote:
> > As multilingual content grows, interlanguage links become
> > longer on Wikipedia articles. Articles such as "Barak Obama"
> > or "Sun" have more than 200 links, and that becomes a problem
> > for users that often switch among several languages.
> >
> >
> > As part of the future plans for the Universal Language
> > Selector, we were considering to:
> > * Show only a short list of the relevant languages for
> > the user based on geo-IP, previous choices and browser
> > settings of the current user. The language the users
> > are looking for will be there most of the times.
> > * Include a "more" option to access the rest of the
> > languages for which the content exists with an
> > indicator of the number of languages.
> > * Provide a list of the rest of the languages that users
> > can easily scan (grouped by script and region ao that
> > alphabetical ordering is possible), and search
> > (allowing users to search a language name in another
> > language, using ISO codes or even making typos).
> > I have created a prototype to illustrate the idea. Since this
> > is not connected to the MediaWiki backend, it lacks the
> > advanced capabilities commented above but you can get the
> > idea.
> > If you are interested in the missing parts, you can check the
> > flexible search and the list of likely languages ("common
> > languages" section) on the language selector used
> > at http://translatewiki.net/ which is connected to MediaWiki
> > backend.
> >
> >
> > As part of the testing process for the ULS language settings,
> > I included a task to test also the compact interlanguage
> > designs. Users seem to understand their use (view recording),
> > but I wanted to get some feedback for changes affecting such
> > an important element.
> >
> >
> > Please let me know if you see any possible concern with this
> > approach.
> >
> >
> >
> > Thanks
> >
> >
> >
> >
> > --
> > Pau Giner
> > Interaction Designer
> > Wikimedia Foundation
> >
> >
> >
> >
> > --
> > Pau Giner
> > Interaction Designer
> > Wikimedia Foundation
> > _______________________________________________
> > Design mailing list
> > Design(a)lists.wikimedia.org
> > https://lists.wikimedia.org/mailman/listinfo/design
>
>
> _______________________________________________
> Design mailing list
> Design(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/design
>
--
Pau Giner
Interaction Designer
Wikimedia Foundation
Hello,
This is a reminder that the Language Engineering team will be hosting
a bug triage session today, i.e. 24th of April 2013 at 1700 UTC/1000
PDT on #mediawiki-i18n (Freenode). The bug list is at
http://etherpad.wikimedia.org/BugTriage-i18n-2013-04 . Event details
can be found be in the section below.
Thanks
Runa
What: Translation User Interface bug triage
Date: April 24 2013
Time: 1700-1800 UTC, 1000-1100 PDT (Timezone conversion: http://hexm.de/r0)
Channel: #mediawiki-i18n (Freenode)
Etherpad: http://etherpad.wikimedia.org/BugTriage-i18n-2013-04
Questions can be sent to: runa at wikimedia dot org
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Sat, Apr 20, 2013 at 1:02 AM
Subject: [Language Engineering] Bug triage on Wednesday, April 24 2013
at 1700 UTC/1000 PDT
To: mediawiki-i18n(a)lists.wikimedia.org, Wikimedia Mailing List
<wikimedia-l(a)lists.wikimedia.org>, wikitech-l(a)lists.wikimedia.org
What: Translation User Interface bug triage
Date: April 24 2013
Time: 1700-1800 UTC, 1000-1100 PDT (Timezone conversion: http://hexm.de/r0)
Channel: #mediawiki-i18n (Freenode)
Etherpad: http://etherpad.wikimedia.org/BugTriage-i18n-2013-04
Questions can be sent to: runa at wikimedia dot org
Hello,
The Language Engineering team would like to invite everyone for the
upcoming bug triage session on Wednesday, April 24 2013 at 1700 UTC
(1000 PDT). During this 1 hour session we will be using the etherpad
listed above to collaborate. We have already listed some bugs, but
please feel free to add more bugs, comments and any other related
issues that you’d like to see addressed during the session. You can
send questions directly to me on email or IRC (nick: arrbee). Please
see above for event details.
Thank you.
regards
Runa
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
What: Translation User Interface bug triage
Date: April 24 2013
Time: 1700-1800 UTC, 1000-1100 PDT (Timezone conversion: http://hexm.de/r0)
Channel: #mediawiki-i18n (Freenode)
Etherpad: http://etherpad.wikimedia.org/BugTriage-i18n-2013-04
Questions can be sent to: runa at wikimedia dot org
Hello,
The Language Engineering team would like to invite everyone for the
upcoming bug triage session on Wednesday, April 24 2013 at 1700 UTC
(1000 PDT). During this 1 hour session we will be using the etherpad
listed above to collaborate. We have already listed some bugs, but
please feel free to add more bugs, comments and any other related
issues that you’d like to see addressed during the session. You can
send questions directly to me on email or IRC (nick: arrbee). Please
see above for event details.
Thank you.
regards
Runa
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hello,
The Wikimedia Language Engineering team announced the launch of the
the pilot phase of the Language Maven outreach program during their
recent IRC office hour[1]. To kick-off the program, the team hosted an
online meeting with some of the Language Mavens where matters related
to the scope of the project were discussed. It was also proposed to
prepare checklists of the available tools and other related items that
can be used by the Mavens as ready-reckoners. Another meeting has been
set to be held during the month of May to be followed thereafter by
regular monthly meetings. The program has met with a positive response
and is expected to bridge the gaps that currently exist between the
Wikimedia projects in different languages. The summary of the
discussions can be found in the meeting notes[2]. Further discussions
will continue on the mediawiki-i18n mailing list.
We would also like to invite more participants into the program.
Please sign up by using the form located at the following link:
http://hexm.de/LangMavenSignUpForm
More details about the program can be found in the mediawiki page[3]
and questions can also be sent to the mailing list or directly to me
at: runa at wikimedia dot org
regards
Runa
[1] http://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2013-04-10
[2] http://www.mediawiki.org/wiki/Language_tools/Language_Team_Plan/Language_Ma…
[3] http://www.mediawiki.org/wiki/Language_tools/Language_Team_Plan
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Hoi,
I am the developer of the SignWriting MediaWiki Plugin. It enables a
SignWriting viewer for MediaWiki software. It supports an International
community and can be used for any sign language.
I just released a radically simplified version of the extension in
Gerrit: 20 lines of PHP code and 50 lines of Javascript.
https://gerrit.wikimedia.org/r/gitweb?p=mediawiki/extensions/SignWritingMed…
I am hoping someone can look over the code and point out any flaws.
I'm hoping it can be deployed on Incubator. I reopened a bug from long ago.
https://bugzilla.wikimedia.org/show_bug.cgi?id=22216
The PHP code makes a call to the Resource Module to load
"signwriting_thin.js" (3 KB file). The Javascript runs on the client
side only if Formal SignWriting is detected on the page.
There shouldn't be any security problems for the server running this
extension and there is a miniscule cost to the user's browser.
The MediaWiki extension is a wrapper for the SignWriting Thin Viewer
available on http://SignPuddle.com
Thanks for your consideration,
∼Steve
hi,
the freeplane project (http://freeplane.sourceforge.net) is currently
using mediawiki 1.14.1.
>From this page:
http://www.mediawiki.org/wiki/Extension:Translate
I derive that it's probably only supported in >= 1.19. Is this true?
What is the easiest way to make this (or a similar extension) work with
mediawiki 1.14.1 (of course while keeping the existing pages)?
Currently we have only English pages, but the Freeplane user base is
growing so we need French pages as well.
Thank you! Best Regards,
--
Felix Natter
<https://www.mediawiki.org/wiki/Localisation#Update_of_localisation>
will not be true for a short while.
Nemo
-------- Messaggio originale --------
Oggetto: [Wikitech-ambassadors] Temporarily disabling l10n update
Data: Wed, 10 Apr 2013 13:01:12 -0700
Mittente: Rob Lanphier
Hi folks,
We've had at least a couple of site outages which we believe are due
to l10nupdate. The root cause is identified in a fairly old
ResourceLoader bug that seems to be biting us a little harder than it
normally does:
https://bugzilla.wikimedia.org/show_bug.cgi?id=27320
Disabling l10nupdate means that changes from Translatewiki.net will
not propagate to our websites as quickly as they normally do.
Depending on how long it takes us to fix this, it could be multiple
days.
Brad Jorsch is going to take a closer look at this issue
today/tomorrow, and hopefully identify the root cause. If he's able
to find the cause quickly, we may not need to disrupt the service, but
we're going to plan for the worst here.
Thanks (in advance) for your patience!
Rob
_______________________________________________
Wikitech-ambassadors mailing list
Wikitech-ambassadors(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
*
Hello,
*
*
*
*
This is a reminder that the Language Engineering team will be hosting an
IRC office hour today, i.e. 10th of April 2013 at 1700 UTC/1000 PDT on
#wikimedia-office (Freenode). The agenda can be found in the section below.
*
*
*
*
Thanks
*
*
Runa
*
*
*
*
Agenda:
*
*
1.
Introductions
2.
Translate UX - Deployment and other news
3.
Language Mavens - an outreach initiative with the Wikimedia language
communities
4.
MediaWiki Language Extension Bundle (MLEB) Release
5.
Q/A - We shall be taking questions during the session. Questions can
also be sent to runa at wikimedia dot org <runa(a)wikimedia.org> before
the event and can be addressed during the office-hour.
*
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Fri, Apr 5, 2013 at 3:07 PM
Subject: [Language Engineering] Office hour on 10th April 2013 at 1700
UTC/1000 PDT
To: mediawiki-i18n(a)lists.wikimedia.org, Wikimedia Mailing List <
wikimedia-l(a)lists.wikimedia.org>, wikitech-l(a)lists.wikimedia.org
*
Hello,
The Wikimedia Language Engineering team [1] invites everyone to join the
team’s monthly office hour on April 10, 2013. We have some exciting updates
about our ongoing projects, some of which have also been shared in our
recent blog posts[2]. During this session we would like to walk through
some of them. The team would also like to introduce a new outreach program
which was mentioned in the last office hour held on 13th March 2013 [3].
Event details and the general agenda is mentioned below.
See you all at the IRC office hour!
regards
Runa
Event Details:
==========
Date: 2013-04-10 (Wednesday)
Time: 1700 UTC, 1000 PDT
IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
1.
Introductions
2.
Translate UX - Deployment and other news
3.
Language Mavens - an outreach initiative with the Wikimedia language
communities
4.
MediaWiki Language Extension Bundle (MLEB) Release
5.
Q/A - We shall be taking questions during the session. Questions can
also be sent to runa at wikimedia dot org <runa(a)wikimedia.org> before
the event and can be addressed during the office-hour.
[1] http://wikimediafoundation.org/wiki/Language_Engineering_team
[2]
http://blog.wikimedia.org/c/technology/features/internationalization-and-lo…
[3] http://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2013-03-13
*
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
*
Hello,
The Wikimedia Language Engineering team [1] invites everyone to join the
team’s monthly office hour on April 10, 2013. We have some exciting updates
about our ongoing projects, some of which have also been shared in our
recent blog posts[2]. During this session we would like to walk through
some of them. The team would also like to introduce a new outreach program
which was mentioned in the last office hour held on 13th March 2013 [3].
Event details and the general agenda is mentioned below.
See you all at the IRC office hour!
regards
Runa
Event Details:
==========
Date: 2013-04-10 (Wednesday)
Time: 1700 UTC, 1000 PDT
IRC channel: #wikimedia-office on irc.freenode.net
Agenda:
1.
Introductions
2.
Translate UX - Deployment and other news
3.
Language Mavens - an outreach initiative with the Wikimedia language
communities
4.
MediaWiki Language Extension Bundle (MLEB) Release
5.
Q/A - We shall be taking questions during the session. Questions can
also be sent to runa at wikimedia dot org <runa(a)wikimedia.org> before
the event and can be addressed during the office-hour.
[1] http://wikimediafoundation.org/wiki/Language_Engineering_team
[2]
http://blog.wikimedia.org/c/technology/features/internationalization-and-lo…
[3] http://meta.wikimedia.org/wiki/IRC_office_hours/Office_hours_2013-03-13
*
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
Here are the current plans for i18n deployment next Tuesday (2013-04-09).
https://bugzilla.wikimedia.org/46840
* Update Translate Solr schema so that Special:SearchTranslations
actually works on Wikimedia sites using Translate.
* If the patch to operations is not merged and deployed in time this
will be postponed or I might request separate deployment window to
rebuild the data.
https://bugzilla.wikimedia.org/46754
* Enable WebFonts on Dhivehi projects (dv.wikipedia and dv.wiktionary)
https://bugzilla.wikimedia.org/43359
* Enable WebFonts on the Javanese projects
https://bugzilla.wikimedia.org/25326
* Devanagari transliteration tool for Bhojpuri Wikipedia
-Niklas