trans September 2008

trans@lists.fedoraproject.org

32 participants
50 discussions

[Bug 454727] New: Transifex module for kf request
by Red Hat Bugzilla 27 Oct '08

27 Oct '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=454727 Summary: Transifex module for kf request Product: Fedora Localization Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: l10n-requests AssignedTo: dimitris(a)glezos.com ReportedBy: lkundrak(a)v3.sk QAContact: aalam(a)redhat.com CC: fedora-trans-list(a)redhat.com Module name: kf Description: kf Jabber Client Project webpage: https://fedorahosted.org/kf/ VCS root,module,branch: svn+ssh://svn.fedorahosted.org/svn/kf/trunk File filter: po/.*\.po Changelog file (if applicable): ChangeLog Web front-end to VCS: https://fedorahosted.org/kf/browser/trunk/po -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 1

Access to new git repos
by Paul W. Frields 18 Oct '08

18 Oct '08

If you are translating content for the Release Notes or Installation Guide that have been relocated to Fedora Hosted, you do *not* need to join any additional Fedora Account System groups. You can submit PO files through Transifex as needed. If you prefer to check out the content manually and provide PO files through Transifex, you can do an anonymous checkout of a repository with this command: git clone git://git.fedorahosted.org/git/docs/release-notes -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

2 2

[Bug 455796] New: Tajik Keyboard Layout (Tajik xkb - tj)
by Red Hat Bugzilla 14 Oct '08

14 Oct '08

Please do not reply directly to this email. All additional comments should be made in the comments box of this bug report. https://bugzilla.redhat.com/show_bug.cgi?id=455796 Summary: Tajik Keyboard Layout (Tajik xkb - tj) Product: Fedora Localization Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: low Priority: low Component: Other language AssignedTo: dimitris(a)glezos.com ReportedBy: victor.ibragimov(a)gmail.com QAContact: aalam(a)redhat.com CC: fedora-trans-list(a)redhat.com Description of problem: There is an official Tajik Standard Keyboard Layout required by the TojikStandard Organization to be used in software development. The official keyboard, due to the added 6 characters, does not support important keys such as _-+= as they are replaced by special characters “ғ” and “ӯ” on Tajik keyboard. For the translators in Linux a Tajik keyboard was developed to match the Russian layout and have all the keys available on the keyboard. This unofficial Tajik keyboard layout use more than one buttons to get a letter with a special sign for Tajik language and require two key strokes. The existing Tajik xkb in Fedora is based on unofficial layout. To meet the requirements/needs for both official and unofficial, the following layout has been created to resolve the existing (but permanent) Tajik layout issues. Steps to Reproduce: 1. Change the existing Tajik xkb (tj) Expected results: // 17/07/2008 // ------------------------------------------------------------- // Standard Tojiki Keyboard Layout, Official Standard // ------------------------------------------------------------- // Created by Victor Ibragimov <victor.ibragimov(a)gmail.com> // Tajik Fedora & Software Localization Team // ------------------------------------------------------------- // DUAL INPUT METHOD // -------------------------------------------------------------------- // -------------- Tojiki Official Keyboard Layout---------------------- // -------------------------------------------------------------------- // partial default alphanumeric_keys xkb_symbols "official" { name[Group1]= "Tojikiston - official"; key <AE01> { [ 1, exclam, 0x10000a7 ] }; key <AE02> { [ 2, quotedbl, 0x10000ab, 0x10000bb ] }; key <AE03> { [ 3, numerosign ] }; key <AE04> { [ 4, semicolon ] }; key <AE05> { [ 5, percent ] }; key <AE06> { [ 6, colon, 0x1002013 ] }; key <AE07> { [ 7, question, ampersand ] }; key <AE08> { [ 8, asterisk ] }; key <AE09> { [ 9, parenleft ] }; key <AE10> { [ 0, parenright, 0x10000b0 ] }; key <AE11> { [ 0x1000493, 0x1000492, minus, underscore ] }; key <AE12> { [ 0x10004ef, 0x10004ee, equal, plus ] }; key <AB10> { [ period, comma ] }; key <BKSL> { [ backslash, slash ] }; key <LSGT> { [ slash, bar ] }; key <TLDE> { [ Cyrillic_io, Cyrillic_IO ] }; key <AD01> { [ Cyrillic_shorti, Cyrillic_SHORTI ] }; key <AD02> { [ 0x100049b, 0x100049a ] }; key <AD03> { [ Cyrillic_u, Cyrillic_U ] }; key <AD04> { [ Cyrillic_ka, Cyrillic_KA ] }; key <AD05> { [ Cyrillic_ie, Cyrillic_IE ] }; key <AD06> { [ Cyrillic_en, Cyrillic_EN ] }; key <AD07> { [ Cyrillic_ghe, Cyrillic_GHE ] }; key <AD08> { [ Cyrillic_sha, Cyrillic_SHA ] }; key <AD09> { [ 0x10004b3, 0x10004b2 ] }; key <AD10> { [ Cyrillic_ze, Cyrillic_ZE ] }; key <AD11> { [ Cyrillic_ha, Cyrillic_HA ] }; key <AD12> { [Cyrillic_hardsign,Cyrillic_HARDSIGN ] }; key <AC01> { [ Cyrillic_ef, Cyrillic_EF ] }; key <AC02> { [ 0x10004b7, 0x10004b6 ] }; key <AC03> { [ Cyrillic_ve, Cyrillic_VE ] }; key <AC04> { [ Cyrillic_a, Cyrillic_A ] }; key <AC05> { [ Cyrillic_pe, Cyrillic_PE ] }; key <AC06> { [ Cyrillic_er, Cyrillic_ER ] }; key <AC07> { [ Cyrillic_o, Cyrillic_O ] }; key <AC08> { [ Cyrillic_el, Cyrillic_EL ] }; key <AC09> { [ Cyrillic_de, Cyrillic_DE ] }; key <AC10> { [ Cyrillic_zhe, Cyrillic_ZHE ] }; key <AC11> { [ Cyrillic_e, Cyrillic_E ] }; key <AB01> { [ Cyrillic_ya, Cyrillic_YA ] }; key <AB02> { [ Cyrillic_che, Cyrillic_CHE ] }; key <AB03> { [ Cyrillic_es, Cyrillic_ES ] }; key <AB04> { [ Cyrillic_em, Cyrillic_EM ] }; key <AB05> { [ Cyrillic_i, Cyrillic_I ] }; key <AB06> { [ Cyrillic_te, Cyrillic_TE ] }; key <AB07> { [ 0x10004e3, 0x10004e2 ] }; key <AB08> { [ Cyrillic_be, Cyrillic_BE ] }; key <AB09> { [ Cyrillic_yu, Cyrillic_YU ] }; include "keypad(comma)" include "level3(ralt_switch)" }; // -------------------------------------------------------------------- // -------------- Tojiki Rusi Keyboard Layout-------------------------- // -------------------------------------------------------------------- // AEN <aen(a)logic.ru> // 2001/12/23 by Leon Kanter <leon(a)blackcatlinux.com> // 2005/12/09 Valery Inozemtsev <shrek(a)altlinux.ru> // Pablo Saratxaga <pablo@mandrakesoft> (for the dead keys changes) // -------------------------------------------------------------------- partial alphanumeric_keys xkb_symbols "tojikirusi" { name[Group1]= "Tojikiston - TojikiRusi"; key <AE01> { [ 1, exclam, 0x10000a7 ] }; key <AE02> { [ 2, quotedbl, 0x10000ab, 0x10000bb ] }; key <AE03> { [ 3, numerosign ] }; key <AE04> { [ 4, semicolon ] }; key <AE05> { [ 5, percent ] }; key <AE06> { [ 6, colon, 0x1002013 ] }; key <AE07> { [ 7, question, ampersand ] }; key <AE08> { [ 8, asterisk ] }; key <AE09> { [ 9, parenleft ] }; key <AE10> { [ 0, parenright ] }; key <AE11> { [ minus, underscore ] }; key <AE12> { [ equal, plus ] }; key <BKSL> { [ backslash, slash ] }; key <AB10> { [ period, comma ] }; key <LSGT> { [ slash, bar ] }; key <TLDE> { [ Cyrillic_io, Cyrillic_IO ] }; key <AD01> { [ Cyrillic_shorti, Cyrillic_SHORTI ] }; key <AD02> { [ Cyrillic_tse, Cyrillic_TSE ] }; key <AD03> { [ Cyrillic_u, Cyrillic_U, 0x10004ef, 0x10004ee ] }; key <AD04> { [ Cyrillic_ka, Cyrillic_KA, 0x100049b, 0x100049a ] }; key <AD05> { [ Cyrillic_ie, Cyrillic_IE ] }; key <AD06> { [ Cyrillic_en, Cyrillic_EN ] }; key <AD07> { [ Cyrillic_ghe, Cyrillic_GHE, 0x1000493, 0x1000492 ] }; key <AD08> { [ Cyrillic_sha, Cyrillic_SHA ] }; key <AD09> { [ Cyrillic_shcha, Cyrillic_SHCHA ] }; key <AD10> { [ Cyrillic_ze, Cyrillic_ZE ] }; key <AD11> { [ Cyrillic_ha, Cyrillic_HA, 0x10004b3, 0x10004b2 ] }; key <AD12> { [Cyrillic_hardsign,Cyrillic_HARDSIGN ] }; key <AC01> { [ Cyrillic_ef, Cyrillic_EF ] }; key <AC02> { [ Cyrillic_yeru, Cyrillic_YERU ] }; key <AC03> { [ Cyrillic_ve, Cyrillic_VE ] }; key <AC04> { [ Cyrillic_a, Cyrillic_A ] }; key <AC05> { [ Cyrillic_pe, Cyrillic_PE ] }; key <AC06> { [ Cyrillic_er, Cyrillic_ER ] }; key <AC07> { [ Cyrillic_o, Cyrillic_O ] }; key <AC08> { [ Cyrillic_el, Cyrillic_EL ] }; key <AC09> { [ Cyrillic_de, Cyrillic_DE ] }; key <AC10> { [ Cyrillic_zhe, Cyrillic_ZHE ] }; key <AC11> { [ Cyrillic_e, Cyrillic_E ] }; key <AB01> { [ Cyrillic_ya, Cyrillic_YA ] }; key <AB02> { [ Cyrillic_che, Cyrillic_CHE, 0x10004b7, 0x10004b6 ] }; key <AB03> { [ Cyrillic_es, Cyrillic_ES ] }; key <AB04> { [ Cyrillic_em, Cyrillic_EM ] }; key <AB05> { [ Cyrillic_i, Cyrillic_I, 0x10004e3, 0x10004e2 ] }; key <AB06> { [ Cyrillic_te, Cyrillic_TE ] }; key <AB07> { [Cyrillic_softsign,Cyrillic_SOFTSIGN ] }; key <AB08> { [ Cyrillic_be, Cyrillic_BE ] }; key <AB09> { [ Cyrillic_yu, Cyrillic_YU ] }; include "keypad(comma)" include "level3(ralt_switch)" }; Additional info: Tajik Dual Input Method -- Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.

1 1

Where is module virt-manager?
by Xavi Conde 06 Oct '08

06 Oct '08

Hi, I was going to send the translation of virt-manager module when I noticed that it is not listed anymore in https://translate.fedoraproject.org/module/. Do you know how can I commit the translation? Thanks in advance! -- HAL I am putting myself to the fullest possible use, which is all I think that any conscious entity can ever hope to do. + Google talk/Jabber: xavi.conde a gmail.com

4 4

New language codes?
by Paul W. Frields 03 Oct '08

03 Oct '08

If the Docs Project is able to complete a transition to Publican for the release notes for Fedora 10, many of our language codes will change to ISO standards. This includes moving from en_US to en-US, as in "Release_Notes-en-US.txt". It would probably be good if any tools used to spin or release the distribution get updated to support both of these options. I would suggest shifting them to use the ISO standard, en-US, first and the try falling back to en_US. That way, if we fail utterly and have to drop back to the old way of doing business, the results will still land properly. -- Paul W. Frields http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 http://redhat.com/ - - - - http://pfrields.fedorapeople.org/ irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug

11 13

virt-top and virt-ctrl POT files!
by Ankit Patel 03 Oct '08

03 Oct '08

Hi Richard, It looks like both the modules virt-top and virt-ctrl share a common POT file. https://translate.fedoraproject.org/POT/virt-ctrl.tip/virt-top.tip.pot (From https://translate.fedoraproject.org/module/virt-ctrl) https://translate.fedoraproject.org/POT/virt-top.tip/virt-top.tip.pot (From https://translate.fedoraproject.org/module/virt-top) Could you please confirm this please? Btw, the modules are not available for translation submission via Transifex. If you would like to receive translations into various languages for these packages please register your modules on Transifex: https://translate.fedoraproject.org/submit/maintainers/info Thanks a lot! -- Regards, Ankit Patel http://www.indianoss.org/

3 2

system-switch-java
by Noriko Mizumoto 01 Oct '08

01 Oct '08

For update, The above module is still unable to submit via Transifex due to the ownership issue [1], waiting for Infra team action.. https://fedorahosted.org/fedora-infrastructure/ticket/826 cheers noriko

6 7

access to DL t.fp.o
by Domingo Becker 30 Sep '08

30 Sep '08

Can anybody help me with this bug ? https://bugzilla.redhat.com/show_bug.cgi?id=464133 It's about the access to http://translate.fedoraproject.org/languages/es/fedora-10 thanks and kind regards Domingo Becker (es)

2 1

Re: F10 Documentation
by Asgeir Frimannsson 30 Sep '08

30 Sep '08

----- "Asgeir Frimannsson" <asgeirf(a)gmail.com> wrote: > On Tue, Sep 30, 2008 at 3:13 AM, Dimitris Glezos <dimitris(a)glezos.com> > wrote: > > 2008/9/29 Paul W. Frields <stickster(a)gmail.com>: > >> On Mon, Sep 29, 2008 at 05:19:14PM +0530, Ankitkumar Rameshchandra > Patel wrote: > >>> Dimitris Glezos wrote: > >>>> 2008/9/26 Paul W. Frields <stickster(a)gmail.com>: > >>>> > >>>>> On Fri, Sep 26, 2008 at 12:08:31PM +0300, Dimitris Glezos > wrote: > >>>>> > >>>>>> We'll need the usual steps followed to add these modules to > transifex: > >>>>>> > >>>>>> http://fedoraproject.org/wiki/L10N/FAQ#add-transifex > >>>>>> > >>>>>> The most important ones are having 'transif' added to the > respective > >>>>>> account system groups and notifying us with which <VCS root, > module, > >>>>>> branch> to use. One bug report for all moved Docs would be > sufficient, > >>>>>> and we can re-open it when a new module has been moved. > >>>>>> > >>>> All 7 docs projects have been registered and enabled [1] in > Transifex. > >>>> > >>>> https://translate.fedoraproject.org/submit/module/ > >>>> > >>> > >>> Can we get all 7 docs projects enabled in DL as well? > >> > >> I think Dimitris mentioned earlier that Damned Lies won't support > >> Publican's multiple POT files. It would be great if Red Hat > I18n/L10n > >> would collaborate with the community to help pave the way for > >> statistics reporting for these repos. I don't know whether that > means > >> fixing part of DL, or simply accelerating the rate at which > >> statistical support in Tx is written. I know Dimitris, Asgeir, > and > >> any of the other Tx developers would be thrilled to have some > >> assistance with this. > > > > Patches are welcome with champagnes and fireworks, as always. :D > > > >> In the meantime, Dimitris also suggested a workaround using some > sort > >> of simple Python script. I doubt that's been written yet, maybe > >> someone can help there? > > > > Here's a sample skeleton for such a script/scenario, for anyone > who'd > > like to actually code it. > > > > ----------------------- > > == Get the source == > > > > First time: > > $ project-list = ['about', 'release-notes'] > > $ for p in project-list: > > git clone git://git.fedoraproject.org/git/{p}.git > > > > Later, to pull new changes: > > $ for p in project-list: > > git fetch && ... > > > > == Calculate statistics == > > $ wget http://.../fedora-docs-l10n-script.py > > $ python fedora-docs-l10n-script.py pt_BR > > pt_BR statistics: > > about: 80% (115T, 40F, 10U) > > release-notes: 80% (115T, 40F, 10U) > > ----------------------- > > If I remember correctly, publican actually has a 'genearate > translation statistics' make target that can even generate HTML. > > Would it be ok If I set up a cron job that: > 1) Puts translation statistics on a public web page (to make it > simple, e.g. my fedorapeople web space) > 2) Sends updated statistics to fedora-trans-list daily, or even after > each 'submission' depending on how much we want to spam that list... > > In addition, we could add a link to this stats through the front page > of translate.fedoraproject.org > > Comments on this workflow is welcome, but I'll try to make sure we at > least have some statistics for our documentation SOON. > > I guess the fedora infrastructure is in 'freeze' mode, so I'm not > sure > how easy it would be to make the script run inside the > infrastructure... But the main concern now is giving translators some > statistics :) > > But first for some breakfast... Could anyone review the attached script for converting release-notes to a publican-friendly PO structure? Figured I'd learn ABC in bash scripting while I was at it... I could send out a git patch, but it makes it a bit hard to see what I was doing... cheers, asgeir

2 1

Tuning Documentation & Translation schedules
by John Poelstra 30 Sep '08

30 Sep '08

Thanks for being patient with me as I get up to speed with the different tasks your teams perform and where they intersect. I am continually refining the wording of each task so it is hopefully clearer exactly what is being done. In the process I'm discovering more undocumented tasks that need to be completed to bridge tasks already on the schedule and also finding others that are unclear as to what they are. For example we say "translations due" but we don't say which translations they are... release notes, softare, documentation? I am also trying to a better job of representing on each team's schedule which tasks THEY perform. For example the Documentation schedule lists only the tasks that docs is responsible for--not translation tasks too. The overall schedule shows combined tasks for all the teams if you're looking for a combined view. On Monday at 16:00 UTC I'll be meeting Demitris on fedora's gobby instance to add more details and corrections to the Fedora 10 translation schedule. Feel free to join in. If this turns out to be helpful I would like to do a similar exercise with the docs team if they are so interested. Translation schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-trans-tasks.html Docs schedule: http://poelstra.fedorapeople.org/schedules/f-10/f-10-docs-tasks.html John

4 7

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans September 2008