Hi All,
I am sure, most of the people working with Fedora I18N, L10N from 5-6
year must be aware regarding Fedora L10N Steering Committee. [1] As far
as i know this committee was active around 2009 and very effective.
During Fedora G11N activity day discussions, we again felt there is
need for some kind of official committee to drive Fedora Globalization
activities. Fedora is growing faster with number of different domains
and G11N also need to adapt those changes quickly to remain on the track.
For this purpose and in line with [1], we were thinking of Fedora
Globalization steering committee. I have created initial proposal for
it. [2]
Its open for feedback, please feel free to share other active members,
discuss in your respective language groups. This is just initial
proposal and i am sure, we can improve and make it more effective with
active participation.
Regards,
Pravin Satpute
1.
https://fedoraproject.org/wiki/L10N_Steering_Committee?rd=L10N/SteeringComm…
2. https://fedoraproject.org/wiki/Fedora_G11N_Steering_Committee_Proposal
_______________________________________________
g11n mailing list
g11n(a)lists.fedoraproject.org
http://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
Hi,
My name is Alex Eng and I'm from Zanata team.
Apart from engineering, I'm interested in working in translations too for
Fedora.
I'm fluent in Simplify Chinese, Malay, English, and Traditional Chinese but
I would start with Simplify Chinese for the time being.
https://fedoraproject.org/wiki/User:Aeng
--
Alex Eng
Hi all,
I am sure many members involved in trans, i18n, zanata and fltg will be
there. This is good chance to have couple hours meetup and review present
state and plan for coming 2 releases of Fedora.
I have created page for g11n flock 2016 [1]. Please add your name on
page and add topic if anything in mind.
Thanks,
Pravin Satpute
1. https://fedoraproject.org/wiki/G11N/Meetup_Flock_2016
https://bugzilla.redhat.com/show_bug.cgi?id=1236278
Bug ID: 1236278
Summary: Update the words in Marathi spell check
Product: Fedora Localization
Component: Other language
Severity: low
Assignee: dimitris(a)glezos.com
Reporter: shantanu.oak(a)gmail.com
QA Contact: aalam(a)redhat.com
CC: dimitris(a)glezos.com, piotrdrag(a)gmail.com,
trans(a)lists.fedoraproject.org
Description of problem:
The words found in current hunspell are not enough.
Version-Release number of selected component (if applicable):
All versions
How reproducible:
Try marathi spell check in Libre office.
Actual results:
Unsatisfactory options
Expected results:
Better suggestions.
Additional info:
Add all the verified words from this link:
http://bit.ly/1NmNMJd
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=C8kMP3BVwj&a=cc_unsubscribe
Hello everyone,
in the past we have had a tradition of sponsoring EMEA contributors that would like to attend Flock[0] but are not going to receive funding as speakers.
The allocated budget for this year was only $800, initially. The adjusted budget is even less. As we wish to assist as many contributors in need as possible, we are going to try and raise that budget. However, no promises made at this point.
This program is intended for contributors that currently reside in EMEA. Other regions may feel free to come up with similar programs for their contributors as they see fit. Priority will be given to contributors that have recently maintained a record of activity and also have some kind of work agenda for the conference (e.g. meet with fellow contributors, actively contribute on site).
In any case, the budget we are going to end up with will be limited. Most likely we will be able to offer only -partial- subsidies. Do not apply if you are not okay with that. If you are able to receive funding from other sources (e.g. your employer), please do so.
To request for sponsorship, file a ticket on the EMEA Trac[1], state the reason(s) for applying and what you expect to accomplish by attending the conference. Deadline should be July 5, 23:59:59 UTC +0. All tickets will be later evaluated by FAmSCo, same as last time.
We will get back to you once we have more information regarding the budget. Please spread the news to your fellow Fedorians.
Thank you and good luck!
-Giannis
[0] https://flocktofedora.org/
[1] https://fedorahosted.org/emea-swag-tracking/
--
Giannis Konstantinidis
giannis(a)konstantinidis.cc
http://konstantinidis.cc
giannisk on irc.freenode.net
On 2016年06月28日 21:46, pravin.d.s(a)gmail.com wrote:
> Hi All,
>
> Next Tuesday is System-wide change submission deadline. [1] As we
> decided last week, proposing meeting tomorrow to make sure all our
> planned changes [2] get ready before it.
>
> If there are any more idea, please upload to ticket. For trans we
> already have ticket at [3]
I don't know how L10n team to involve this change submission, but I do
have two items for F25 Planning, which I probably can take a lead, thus
added. I like to hear more from other input from other translators and
coordinators for F25 Localization.
noriko
>
> Thanks,
> Pravin Satpute
>
> 1. https://fedoraproject.org/wiki/Releases/25/Schedule
> 2. https://fedorahosted.org/i18n/ticket/64
> 3. https://fedorahosted.org/G11N/ticket/24
>
>
> _______________________________________________
> g11n mailing list
> g11n(a)lists.fedoraproject.org
> https://lists.fedoraproject.org/admin/lists/g11n@lists.fedoraproject.org
>
Bonjour,
j'aimerais vous proposer un projet, à minima francophone, idéalement
multilingue : traduire titre et description des logiciels dans le
magasin d'applications GNOME-Logiciels.
L'idée est de rendre plus accessible l'ensemble de la logithèque mise à
disposition par la communauté Fedora.
Pour se faire : chaque projet doit posséder un fichier [appdata] (le nom
de la norme freedesktop est appstream), et celui ci doit être inclus
dans l'empaquetage rpm de celui-ci.
D'ailleurs, la [traduction de ces fichiers] est prévue dans cette
spécification.
Comme il y a des milliers de logiciels, cette tâche simple devient tout
de suite plus compliquée en termes de coordination et de suivi.
En termes de processus :
* il faut remonter jusqu'au projet source
* trouver son lieu de traduction (peut être une plateforme de
traduction, un logiciel dédié ou même simplement par fichier)
* demander d'inclure cette traduction dans les nouvelles versions du
logiciel (voire demander d'en publier une)
* demander aux mainteneurs du rpm d'inclure le fichier appdata dans leur
[empaquetage]
Quelle source de données ?
Richard Hughes, un des développeurs de GNOME-Softwares produit avec son
outil [appstream-glib], une série d'[extractions xml] sur lesquelles
nous pouvons mesurer notre avancement.
Pour information, il y a quelques mois j'avais produit quelques
[statistiques] (à l'époque sur 613 paquets F23, nous avions 28% des
logiciels de la catégorie "desktop" dont les descriptions étaient
traduites et 18% si on prend toutes les catégories de logiciels (il y a
aussi des extensions, des polices de caractère, des pilotes, etc.).
Je recherche actuellement une solution logicielle permettant de générer
facilement un tableau de bord montrant l'avancement, et permettant de
saisir des liens vers les tickets de suivi.
Si quelqu'un sait faire quelque chose de simple et d'automatique cela
serait génial.
L'objet de ce projet n'est pas d'augmenter la quantité de projets dans
la logithèque (ajout des appdata), mais de traduire ceux ayant déjà
présents.
Il ne s'agit pas non plus de traduire tous les logiciels disponibles,
mais de faciliter leur accessibilité en rendant compréhensible /
recherchable leurs descriptions.
Si l'un amène l'autre, c'est très bien, mais ce n'est pas l'objectif
principal (je pense cependant que cela permettra d'augmenter le besoin
de traduction de certains).
Voilà pour la présentation, maintenant il faut en discuter et itérer
collectivement :
* le projet et son approche vous semblent-t-ils bien pertinents ?
* avez-vous envie de voir ce projet réussir en donnant un coup de main ?
[appdata]
https://www.freedesktop.org/software/appstream/docs/chap-Quickstart.html
[traduction des fichiers]
https://www.freedesktop.org/software/appstream/docs/sect-Quickstart-Transla…
[empaquetage] https://fedoraproject.org/wiki/Packaging:AppData
[appstream-glib] https://github.com/hughsie/appstream-glib
[extractions xml] https://alt.fedoraproject.org/pub/alt/screenshots/f24/
[statistiques]
https://fedoraproject.org/wiki/User:Jibecfed#AppData_.2F_AppStream_Statisti…
--
Jean-Baptiste Holcroft
Hi
As we know, new coordinator joins or a coordinator is changed, he/she
follows this page 'L10n Maintainer' [1]. I am not sure from when, but
the steps 'Bugzilla' section no longer work. I have had some
investigation and discussion with Infra, and eventually Infra team now
decided not to use owners.git list.
This section has been updated. If any of language coordinator who likes
to have their own language component, please check the section.
[1]:https://fedoraproject.org/wiki/L10N_Maintainer
cheers
noriko
Dear translators,
tomorrow we will enter June and we will be 2 weeks before F24 GA release
date. We have some important changes on the websites and need to enter a PO
freeze for the websites in production.
We have a new Spin on labs.fedoraproject.org (Astronomy) and some minor
changes through all other websites.
I'm still not sure if we are able to make a new website for secondary
arches in time for F24 GA, if not we will postpone this task until F25
Alpha.
Please take a look at the new source files and try to translate at least
the main websites. The string freeze will block all your strings on
production, but you can check your work in the staging instances, where you
can see also the context of all strings.
We are building actually stg.getfedora.org, labs.stg.fpo, spins.stg.fpo and
arm.stg.fpo in staging.
For any questions or issues please open an issue on
pagure.io/fedora-websites or in our trac [1].
[1] https://fedorahosted.org/fedora-websites/
Thank you and happy translating.
--
Robert Mayr
(robyduck)