I am sure, most of the people working with Fedora I18N, L10N from 5-6
year must be aware regarding Fedora L10N Steering Committee.  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 , we were thinking of Fedora
Globalization steering committee. I have created initial proposal for
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
g11n mailing list
My name is Alex Eng and I'm from Zanata team.
Apart from engineering, I'm interested in working in translations too for
I'm fluent in Simplify Chinese, Malay, English, and Traditional Chinese but
I would start with Simplify Chinese for the time being.
Bug ID: 1236278
Summary: Update the words in Marathi spell check
Product: Fedora Localization
Component: Other language
QA Contact: aalam(a)redhat.com
CC: dimitris(a)glezos.com, piotrdrag(a)gmail.com,
Description of problem:
The words found in current hunspell are not enough.
Version-Release number of selected component (if applicable):
Try marathi spell check in Libre office.
Add all the verified words from this link:
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
* Name: Ana Mativi
* Location: Porto Alegre, Brazil
* Login: mativi
* Language: pt_br
* Profession or Student status: Undergraduate, Computer Engineering
* About You: I'm an undergraduate researcher at the Informatics
Institute of the Federal University of Rio Grande do Sul (UFRGS), in
the video coding area (more info can be found at ).
* You and the Fedora Project: I'm engaged in Fedora activities for
about a year now. I want to join this team because lots of people
need everything to be translated to be able to use Fedora. I'm most
active as an ambassador, but I want to contribute to the websites
team in the near future as well.
* GPG KEYID and fingerprint: pub 2048R/B537B92C 2016-04-25
Key fingerprint = 0D1A 8EFE 075E 0149 6ABD 2505 8C60 FB48
Ana Mativi | FAS: Mativi | IRC: anamativi
Fedora Ambassador (Porto Alegre - BRAZIL)
It's not clear how the branches are related throughout multiple release cycles.
Fixing a translation error, do I have to edit all the branches I can
find? What is master branch for? How is it related f24-branch? Where
do I put fixes? Are rhel*-branches to be translated?
When translate comps, I see two sentences "Packages mandatory for the
server product." and "Packages mandatory for the workstation product."
Are the "server" and "workstation" in these sentences refer to "Fedora
Server" and "Fedora Workstation" respectively?
I guess so, what's your opinion?
Fedora Project Contributor
Would you like to ask to be able to translate Fedora Developer Portal ?
Like every Fedora Website, I don't see any particular reason not to
Website sub-project said they would first test if it is a usefull
If they improve this website, I assume it is.
May I ask website team to push .po files in Zanata ?
Note : I think using google analytics is agains Fedora core values, is
there a precedent ?
-------- Message transféré --------
Sujet : Preparing a new release of Fedora Developer Portal - asking for
Date : Wed, 20 Apr 2016 13:39:11 +0200
De : Adam Samalik <asamalik(a)redhat.com>
Pour : developer-portal(a)lists.fedoraproject.org
Copie à : devel(a)lists.fedoraproject.org,
websites(a)lists.fedoraproject.org, Pavel Valena <pvalena(a)redhat.com>
we have prepared a new release of Fedora Developer Portal, and we would
like to hear your feedback before pushing it into production. If
everything goes fine, we would like to make the release on Monday, April
This email is the first of its kind. I would like to send it every time
before release - to make sure, that we involve everyone who might be
interested. This time, I have also cc-ed 'websites' and 'devel' lists.
All future emails about new releases will go to the 'developer-portal'
mailing list only.
Current version: https://developer.fedoraproject.org/
New release in staging: https://developer.stg.fedoraproject.org/
- refreshed look with more uniform layout
- images in the header have been compressed
2) 'Edit this page' button on every page
- clicking this button gets you to the github repo, where you can
edit the content directly in your web browser and submit a pull-request
3) Including empty pages
- pages are shown with 'help needed' badge
- goal of this is to encourage people/make it easier to contribute
4) Start section
- including guides about Arduino and mobile applications using
Google Android Studio
5) Share your knowledge banner on each page
- with link to our contributing guides:
6) Using Google Analytics
- disabled 'demographics and interest reports'
- disabled 'enhanced link attribution'
- disabled 'remarketing'
- disabled 'advertising reporting features'
- basically, I want to use it only to track views and to see what is
I welcome any feedback or comments.
Have a great day,
Associate Software Engineer
Dear translator teams,
Please have a look to comps strings, many teams have a few words left to
translate : https://fedora.zanata.org/iteration/view/comps/master
100% : fr,pl,uk
99% : zh-CN, es, nl,ru,
95% : de
83% : bg, zh-TW, cs,en-GB,hu,ia,it,ja,pt,pt-BR,sr,sk,sv
=> note : 7% has to be validated by those teams, you may jump to 90%
tranlated/fuzzy/untranslated : 134738 / 12051 / 171 177
Easy real word testing : take a net install, you will have a list of
packages to select in anaconda's main screen : "Software selection". The
translated strings will appear in that menu.
Note : as translation deadline is passed, it may not go to first F24
images. If some translation are done, I'll ask for package update, if
maintainer refuse, it will go to the next production of fedora image.
Thanks for your help
The French translation team had issues with translating documentation.
We didn't know what is up to date and need to be translated, nor could
have an overview of work-in-progress translation.
José (jaaf64) created two pages :
* a [how-to] that explains the production of translated documentation
from translated po files (this allows reviewers to see the translated
messages in their final context)
* a [tracker] to help coordination and information exchange between
doc team and translation team.
The tracker is the most important piece. It aims at sharing :
* information about what is up to date and what is not,
* guide translation priorities
* explanation about why things are read-only
* Zanata direct links to projects
* project specific guidance from owners toward translators
Can you please give your feedback about this pages before we start
conversation with docs team ?
If some docs/trans contributors are available, we would like to take the
opportunity to discuss this at Flock Krakow this summer.
Note : we asked to push french translations of some docs, but never
received an answer, does other groups have completed translations that
aren't pushed to docs.fedoraproject.org ?
Thanks by advance,
please find below my application for the translations team.
Name: Gabriele Spina
Location: Turin, Italy
Profession or student status: Telecommunications Engineer
About You: I work in a multinational mobile communications company. I love
open source and Linux especially. For this reason I'd like to go deeper in
my Linux knowledge and give my contribution to the community. I used some
different distributions in the past (Ubuntu, Debian, Arch Linux), now
landed to Fedora and found my balance.
You and the Fedora Project: Translation is the first step to get involved
in the community, but I would like to increase my skills and give my
contribution also from a technical side. There are so many interesting
GPG KEYID and fingerprint: CAC90A95 Key fingerprint = EECD D244 6F0E 2665
3CC7 1BC8 CD70 A9FA CAC9 0A95