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
Dear translators,
the internationalization of the Fedora Documentation has seen some
progress.
1. the homepage conversion is now complete, it doesn't contain markup
anymore! But sorry, you have to translate it again.
2. I configured all projects in the translation platform All projects
start with "fedora-docs-l10n"
Translating everything means a lot of work: 92 375 messages containing 1
784 225 words.
There is a lot of duplication in some docs (install guide, admin guide,
...), but if a single person had to do this, it would represent an
effort of 112 days (with 8h of work per day and 2000 words/hour).
In terms of priority, I suggest:
1. Homepage:
https://translate.fedoraproject.org/projects/fedora-docs-l10n-docs/
2. Project description:
https://docs.stg.fedoraproject.org/en-US/project/
3. User facing content (teams descriptions, release notes, how-tos,...)
4. Dev content (packaging guideline, install guide, administrator
guide,...)
The global mindset I decided to apply: there is no content not worth
translating. Only you decide if it worth it or not.
I don't expect any language to reach 100%. Don't force yourself, just do
what you like.
Next step is publication, which is under Adam's responsibility (I also
asked for help from one addition infrastructure team member).
By the way, following the simple doctrine "friends of my friends are my
friends", I suggested Asciidoc.org to reuse our system for their
translation, and offered to host them in our translation platform.
After all, it's thanks to Asciidoc and Antora that we have a
documentation system. It's my way to say thank you.
Jean-Baptiste
Hi all,
it's been a week since I mailed my chosen language teams offering my
help but, as of today, I haven't yet got an answer. Maybe I missed some
step along the registration process.
I don't have "Start new translation" button for libosinfo project's components. See attachments for this situation and another project with the button available to start a new translation.
Thanks, have a nice day.
--
Oğuz Ersen
Sent with ProtonMail Secure Email.
*Name:* Harry
*Location:* San Jose, CA, US (Was born in Beijing, China)
*Language:* Simplified Chinese
*About Me:* Hi, my name is Harry and I love fedora, I mainly use Fedora to
do OI (Olympiad in Informatics) problems and prepare for USACO. I can say
that Fedora provided me a stable & good platform and I think it is time to
contribute. However, my coding skills, are mainly bare algorithm related
and it may not be very useful for contributing to fedora project (since
bare algorithms are very far away from the reality), so I think I may use
my bilingual advantages to help translate.
I was born in Beijing, but now I am studying in San Jose. Chinese is my
native language and I can use it to express ideas very fluently. I can use
English for daily conversation & school, (By the way, I got A in my recent
Language Arts grade) I love reading technology related text in English
(especially about operating systems). I acknowledge that I may not be able
to use English to express my self as a native speaker, but I think I can
"well-understand" the sentence in English and translate them to Chinese. I
actually tried to do some translation on translate.fedoraproject.org before
I wrote this email and I think I can deal with that.
*You and the Fedora Project: *I am interested in the Fedora Education &
Fedora Games, but Fedora Translation is definitely my first priority.
*GPG KEYID and fingerprint: *gpg --fingerprint 53CFB8157DEF84D0
pub rsa2048 2020-03-19 [SC]
66E3 6999 FF97 5A65 2BB6 44AD 53CF B815 7DEF 84D0
uid [ultimate] Harry Chen <harrychen0314(a)gmail.com>
sub rsa2048 2020-03-19 [E]
Thanks a lot!
Sincerely,
Harry
Dear translators,
two weeks ago, I informed you the Fedora docs are now fully
translatable[0], thanks to infra team, you can now see your translation
on docs.stg.fedoraproject.org.
What you see published is the content from the translated-sources
repo[1]. Please note docs.stg last generation is written on the bottom
of each page: "Last build: 2020-03-11 14:12:17 UTC".
The scripts updating the translated-sources repo with your translation
isn't yet automated, I still have to run it manually. But Infra team is
working on it.
Please let me know if you see any localized content generation issues.
Production generation will happen soon.
I took the opportunity to create a l10n page[2].
It's empty on purpose, what do you suggest to document here?
I suggest at least:
* For translators: explain how to join Fedora l10n group
* For devs: explain how to request project hosting on translate.fpo
Jean-Baptiste
[0]
https://lists.fedoraproject.org/archives/list/trans@lists.fedoraproject.org…
[1] https://pagure.io/fedora-docs/translated-sources/
[2] https://docs.stg.fedoraproject.org/en-US/localization/