i18n September 2013

i18n@lists.stg.fedoraproject.org

3 participants
8 discussions

#26: proposal: move to using IMEs for ASCII/Latin input
by Fedora Internationalization 06 Jul '14

06 Jul '14

#26: proposal: move to using IMEs for ASCII/Latin input -----------------------+------------------- Reporter: petersen | Owner: i18n@… Type: meeting | Status: new Priority: major | Keywords: Blocked By: | Blocking: -----------------------+------------------- = phenomenon = Currently in Fedora for languages with non-Latin scripts we normally switch between a xkb layout as an input source for inputting Latin/ASCII characters and an IME for inputting native characters. ibus-kkc and ibus-libpinyin both have Latin ("English") input methods. I think it is more natural for primary users of these IMEs to use them by default for Latin character input. So I want to suggest that for F21 we could default Japanese input to use only the kkc IME and Chinese to libpinyin IME, ie no additional keyboard layout source would be needed. Multilingual users might still need an additional keyboard layout input source and that is still fine. Other IMEs might also be extended to support Latin input modes in the future: initially we could do it for those default IMEs that support it. For example I am already using ibus-kkc for both Latin and Japanese input and it works well - I toggle easily between direct and ja input. Perhaps the only change needed for the current IMEs with Latin mode might be input mode state caching, ie using the same mode as last time. -- Ticket URL: <https://fedorahosted.org/i18n/ticket/26> Fedora Internationalization <http://fedorahosted.org/i18n/> Fedora i18n Project

1 20

#25: Bugs Corner
by Fedora Internationalization 19 Mar '14

19 Mar '14

#25: Bugs Corner -----------------------+------------------- Reporter: petersen | Owner: i18n@… Type: meeting | Status: new Priority: major | Keywords: Blocked By: | Blocking: -----------------------+------------------- This bug is for proposing any i18n bugs to be discussed during the Bugs Corner section of the weekly irc meeting. To bring up a Fedora bug for discussion just paste the bugzilla url into this ticket. (This ticket may be used for during the F20 development cycle.) -- Ticket URL: <https://fedorahosted.org/i18n/ticket/25> Fedora Internationalization <http://fedorahosted.org/i18n/> Fedora i18n Project

1 9

#23: Fedora 20 i18n test day
by Fedora Internationalization 21 Nov '13

21 Nov '13

#23: Fedora 20 i18n test day ----------------------+------------------- Reporter: tagoh | Owner: i18n@… Type: meeting | Status: new Priority: major | Keywords: Blocked By: | Blocking: ----------------------+------------------- = phenomenon = It is time to think about i18n test day for f20. for references: Schedule: http://fedoraproject.org/wiki/Schedule QA ticket: https://fedorahosted.org/fedora-qa/ticket/409 -- Ticket URL: <https://fedorahosted.org/i18n/ticket/23> Fedora Internationalization <http://fedorahosted.org/i18n/> Fedora i18n Project

3 25

#24: Fedora 20 i18n docbeats
by Fedora Internationalization 16 Oct '13

16 Oct '13

#24: Fedora 20 i18n docbeats ----------------------+------------------- Reporter: tagoh | Owner: i18n@… Type: meeting | Status: new Priority: major | Keywords: Blocked By: | Blocking: ----------------------+------------------- = phenomenon = it is time to think about updating i18n docbeats. for references: i18n docbeats: https://fedoraproject.org/wiki/Documentation_I18n_Beat Schedule: http://fedorapeople.org/groups/schedule/f-20/f-20-docs- tasks.html Workflow: https://fedoraproject.org/wiki/Docs_Project_workflow_- _beat_writing Style guide: https://fedoraproject.org/wiki/Docs_Project_Style_Guide -- Ticket URL: <https://fedorahosted.org/i18n/ticket/24> Fedora Internationalization <http://fedorahosted.org/i18n/> Fedora i18n Project

1 3

Fonts with default Fedora installation
by pravin.d.s＠gmail.com 03 Oct '13

03 Oct '13

Hi, Recently i done packaging of google-noto-fonts [1] for Fedora. With this font we got number of new script fonts of Unicode which were not available earlier. [2] Just done editing of comps file and my question is out of these script fonts how many we suppose to install by default. Presently we are following like at least one fonts for each script should be available with default installation, so if anyone while browsing web etc can get correct rendering for his script. But here issue is supporting whole Unicode with default installation will be too much. Might be we should only install fonts for BMP of Unicode and lets have other fonts installed by users when required (we do have feature in Fedora where if any fonts are not installed by default fontconfig search for particular script fonts.) I have done comps editing by keeping above thing in mind. If anyone have other suggestion please let me know. Best Regards, Pravin Satpute 1. https://admin.fedoraproject.org/pkgdb/acls/name/google-noto-fonts 2. http://koji.fedoraproject.org/koji/buildinfo?buildID=456970

4 7

Reminder: i18n meeting 2013-09-26 0600 UTC
by Akira TAGOH 25 Sep '13

25 Sep '13

Hi, We will have Fedora i18n meeting at a time described at the subject, in #fedora-meeting on irc.freenode.net as usual. If you have any topics to discuss there, please file a ticket on https://fedorahosted.org/i18n/ For bugs, please add URLs to https://fedorahosted.org/i18n/ticket/25 Thanks, --- Akira TAGOH

1 0

#21: Compare different Desktop Environments in Fedora 19
by Fedora Internationalization 21 Sep '13

21 Sep '13

#21: Compare different Desktop Environments in Fedora 19 ----------------------+------------------- Reporter: pnemade | Owner: i18n@… Type: meeting | Status: new Priority: major | Keywords: Blocked By: | Blocking: ----------------------+------------------- = phenomenon = I am just thinking if we should have some comparison for various desktop environments provided in Fedora 19. We have seen new DE are available since last 2 Fedora releases. The comparison is simple like for each DE, what fonts it installed default, what input-methods available (any default), how can one add new ime, how to change/set fonts, what applications are available for managing fonts, etc.. Benefit:- we can have this comparison for people who want to explore other DE and want to know what options are available for their current desktop to new desktop environment. Can you people provide your suggestions on this idea? -- Ticket URL: <https://fedorahosted.org/i18n/ticket/21> Fedora Internationalization <http://fedorahosted.org/i18n/> Fedora i18n Project

1 5

Before the release of Alpha Lohit Devanagari from lohit2 project
by Pravin Satpute 19 Sep '13

19 Sep '13

Hi All, I am hoping now most of the contributors around are aware regarding the lohit2 project. Before the Alpha release of Lohit Devanagari i think it is important to go through once again goals we planned for this project[1]. Goals: * 1. Cleaning Lohit Open type tables.* Highlights are as below - We rewritten all GSUB rules from scratch. - New rules are supporting both deva and dev2 script tag - Done testing on Harfbuzz as well with Uniscribe and its giving expected results. - Kept GPOS tables intact. - Effectiveness and efficiency [2] (sfd file size is down by 28K and Binary file side is down by 4K) Found one bug w.r.t harfbuzz [3] and looking forward to get it resolved soon. Presently it is in know issue list. By Beta we will have some more improvement on this. * 2. Reusable Open type tables.* We got two important suggestions on this line, so below are suggestions and action taken on it. * 1st suggestion* To have feature file separate than shapes .sfd file for easy re-usability of OT rules. - Thanks to AravindaK, he has already done some work on that line[4], so just using those stuff. I have forked this gitrepo and doing some improvement in it. Once done will request Aravinda to merge with his repo. * 2nd suggestion* To follow AGL[5] and to have readable glyph naming. We were also thinking from this perspective. - This has became a bit complex glyphlist.txt [6] suggest names like "kadeva" or uni0915. But we dont want to follow uni0915 as it is not very readable considering our re-usability goals. - {0915 (kadeva) + 094D (viramadeva) + 0937 (ssadeva)} following this create chances of glyph name string more than 31 characters limit. - So present plan is follow above "kadeva_viramadeva_ssadeva" as much as possible and if it goes above 31 characters we will discard "deva" part from glyphname. * 3. Following of existing standards/guidelines* Dont know how many of you aware regarding "Devanagari Script Behaviour For Hindi"[7] Draft, so its basically guideline for Font developers. I have one blog pending on this. Though this is draft mode we are trying to follow this, since it is very informative and prepared after consulting to language experts. This is where we upto, if anything more needed do provide me your feedback. Also need to decide on release version, i think some version with -alpha will work. Best Regards, Pravin Satpute 1. http://pravin-s.blogspot.in/2013/08/project-creating-standard-and-reusable.… 2. Effective means it should work on all supported platform perfectly and efficient means compact and clear rule 3. https://bugs.freedesktop.org/show_bug.cgi?id=69266 4. https://github.com/aravindavk/ 5. https://sourceforge.net/adobe/aglfn/wiki/AGL%20Specification/ 6. http://kaz.dl.sourceforge.net/project/aglfn.adobe/glyphlist.txt 7. http://tdil-dc.in/tdildcTemp/articles/75443Consolidated%20Feedback%20&%20Ob…

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

i18n September 2013