Thanks for this very helpful bug triage report and conducting the session
Look forward to the next one (next month).
On Mon, Jan 23, 2012 at 5:33 AM, Siebrand Mazeland (WMF) <
Please find the report on the latest i18n triage
below. The rough
notes are on etherpad:
Thanks go to the participants liangent, Nemo_bis, srikanthlogic,
OrenBo, ^demon, aharoni, Nikerabbit, santhosh and hexmode.
We covered three main topics: WebFonts, Narayam and Translate.
Support WebFonts for Chinese -- This topic does not yet have a
bugzilla entry. Because of the complexity, it was agreed that Liangent
and Santhosh would discuss firther. Availability of fonts for Chinese
and their potential large size is an issue. This will require some
more discussion to understand the issue more clearly and to think
about solutions -- there are more than 47.000 characters involved.
Liangent suggested Font Subsetting -- creating downloadable fonts
tailored for a pageon the fly -- but there are multiple issues with
Narayam input methods
-- Bamini keyboard map needs fix:
We are looking for a community member to validate the mapping.
srikanthlogic volunteered to track somebody down.
-- Some vowel combination in
Sinhala Wijesekara need to be corrected: We are looking for a
community member to validate the mapping.
-- Narayam IME on fails to
replace English characters on mobile: This report contains at least
two separate issues. For tracking purposes, that's not great; one
should be split off. Because of the multitude of mobile and tablet
devices, each with their own resolution, screen dimension and aspect
ratio, something like "Narayam on mobile" will probably not be a one
size fits all solution, like it is implemented on desktop browsers.
Siebrand will open a discussion with the mobile team on what we think
we can do with input methods on mobile devices.
-- Unwanted activation which
disables user's ability to type: It's unclear how to proceed with
this. We are thinking about something visual in the proximity of the
text area or input field. This needs to be discussed with UI/UX
people. Siebrand will follow up, and UI/UX designers have been CC-ed
on the issue, but have not yet added their thoughts.
-- Add Telugu Transliteration
input method to Narayam: A Telugu community member/developers is
needed to port the existing input method gadget to Narayam. Hexmode
will chase down a tewiki user/dev.
Script to automate transliteration help maps -- This topic does not
yet have a bugzilla entry. srikanthlogic suggested this for
transliteration tables liike
Opinions differ on if this would contribute anything valuable, as
each transliteration schema is different, and these tables may always
need to be created manually. Siebrand to schedule a session to discuss
-- When re-marking translatable
page for translation, old version of the pages might be shown: It
looks like this behaviour is no longer observed. The issue was closed.
-- Support Google Translate V2
API: Google has deprecated and limited use of the Translate V1 API.
We're looking for a volunteer to update the interface, but one has not
been found yet.
-- Page protection leads to issue
in translatable pages: It looks like Translate may be missing a hook
or it might be using the wrong hook. We're planning on asking Roan for
-- Translate popups with
insufficient height: This appears to be an intermittent, but annoying
issue. During the triage no additional understanding has arisen.
Anyone with information that may reliably reproduce this issue is
requested to please add steps and details in bugzilla.
Cheers! In February, there will be another Localisation and
internationalisation bug triage.
Product Manager Localisation
M: +31 6 50 69 1239
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
Localisation-team mailing list