trans October 2018

trans@lists.fedoraproject.org

11 participants
10 discussions

Proposal: Fedora G11N Steering Committee
by Pravin Satpute 26 Jun '20

26 Jun '20

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

10 28

Self-Introduction: Carmen — Esperanto (also: How to add a new language in Zanata)
by Carmen Bianca Bakker 04 Nov '18

04 Nov '18

Hi all, I'm Carmen from Friesland, The Netherlands. I am currently working on GNOME to make the GNOME desktop available in Esperanto. At the current rate, GNOME 3.22 will have its core release (standard apps, core libraries) completely translated into Esperanto, which I am fairly proud of :-) Unfortunately, from the big distributions, only Debian (and its derivatives) have Esperanto available as a choice out of the box. I want to make sure that Fedora also gets that option. Could someone give me a few steps in the right direction to get that ball rolling? I imagine an Esperanto team must be created on Zanata (which is why I have CC'd Michael Moroni, who is listed as coordinator at <https://fedoraproject.org/wiki/L10N_Teams>;). I also imagine some packages need adjusting. I have some experience with RPM packaging from openSUSE's Build Service, so I can probably do that just fine on my own, but I would really appreciate if someone provided me with an overview of the core language packages (or how to find such an overview). I imagine it would be okay to just send a patch to those packages to enable/add Esperanto? Or is this all done automatically? That truly would be magical. A little bit about myself finally: I'm a free software advocate, avid D&D player, software engineering student, FSFE volunteer, and a couple of other things. You can find me at the FSFE booth at SFScon in Bozen/Bolzano, 16 November. Thanks and with kindness, Carmen

4 8

Multi-language forums
by Brian (bex) Exelbierd 20 Oct '18

20 Oct '18

Hi, There are many people on these lists who speak multiple languages or who are students of language. I encourage you to weigh in on a conversation about multi-language support on discussions.fedoraproject.org. We need your voices and your opinions. https://discussion.fedoraproject.org/t/should-we-make-a-spansh-language-cat… Thank you. regards, bex -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org

1 0

Fedora 29 Final Release Readiness meeting
by Ben Cotton 17 Oct '18

17 Oct '18

Dear all, Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 29 Final Release Readiness meeting. This meeting will be held on Thursday, 2018-10-18 at 19:00 UTC. We will meet to make sure we are coordinated and ready for the Final release of Fedora 29. Please note that this meeting will be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may receive this message several times in order to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. For more information, see https://fedoraproject.org/wiki/Release_Readiness_Meetings. View the meeting on Fedocal: https://apps.fedoraproject.org/calendar/Fedora%20release/2018/10/18/#m9380 -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis

1 1

Self-Introduction: Qiyu Yan, Simplified Chinese
by Qiyu Yan 10 Oct '18

10 Oct '18

Name: Qiyu Yan Location: Haidian District, Beijing Login:yanqiyu Language: English About You: Student from UCAS. Knows some C/C++, You and the Fedora Project: Using Fedora on various devices, and want to contribute my own effort GPG KEYID and fingerprint: [Yan@Karuboniru ~]# gpg --fingerprint 78F2F78AD61E7448 pub 2048R/D61E7448 2018-09-26 密钥指纹 = 18BD 8B07 636E 0C2F D3B1 BD70 78F2 F78A D61E 7448 uid Qiyu Yan <Yanqiyu01(a)gmail.com> sub 2048R/886C2AC3 2018-09-26

2 1

arm.fpo website breaks due to bad Danish translation
by Kévin Raymond 08 Oct '18

08 Oct '18

Hi there, I haven't contributed for years now but still checking several things. The websites are building hourly (please check me Robert and Co if I am wrong) and has been crashing for 73hours now. Due to the Danish incorrect translation. Can someone fix this? msgfmt -c -o po/da.mo po/da.po po/da.po:262: number of format specifications in 'msgid' and 'msgstr' does not match msgfmt: found 1 fatal error The string is there at Zanata https://fedora.zanata.org/webtrans/translate?project=fedora-web&iteration=a… Even Zanata mark this translation as bad but users don't know that it fails our websites rebuild... I dunno how to 0) mark as incorrect under Zanata, 1) get the username who last translated.. I have just used the "reject translation" button but don't know its real meaning... @websites shouldn't we improve our Makefile to: "msgfmt -c " in order to avoid the stacktrace (I might send you a patch :/) continue with default po template for that broken language ? Or open a BZ ticket against that team? Or send an email to the mailing list? It just feel bad to be notified that websites build is broken without telling others... Cheers, -- Kévin Raymond (shaiton) GPG-Key: 4C507CDC

2 1

Where are release notes?
by Игорь Горбунов 08 Oct '18

08 Oct '18

HI, All! It's strange, but Fedora Release Notes ( https://fedora.zanata.org/project/view/fedora-release-notes/versions?dswid=…) are still read-only. May be I've missed something and they are available elsewhere? Best wishes, Igor Gorbounov

6 11

dnf bug is now fixed, and waiting for translators
by Noriko Mizumoto 06 Oct '18

06 Oct '18

Hi The bug has been fixed; https://bugzilla.redhat.com/show_bug.cgi?id=1305340 and is waiting for translators to update at zanata. Could you, translators, please check and update? https://fedora.zanata.org/iteration/view/dnf/master?dswid=-4106 noriko

1 0

Re: Translations are coming!
by Jean-Baptiste Holcroft 01 Oct '18

01 Oct '18

Le 2018-10-01 16:20, Petr Bokoc a écrit : > Adam, the proposal looks reasonable. Regarding where to store > translated sources: based on the Antora issue for multilang We decided to have different repositories because Adam think it is more convenient for his CI work and convinced me it will work fine ;) As one repository for all translation file would create multiple issues, we decided to have dedicated repositories to store POT/PO. Please read this page for more details: https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 > Of course, that requires that someone to periodically in the POs from > our translation platform, run the script to apply them to the sources, > and push the translated sources in the correct directory. The process > was fairly manual before with DocBook/publican, too, so it shouldn't > be a huge issue. The "fairly manual" process was a real issue in the past. We had a lot of translation that never been published :( What Adam is working on is: automation. So, we should have something like this: English source -> POT files -> PO files -> translated source -> translated site English source => Doc repository ==> (D) POT files -> PO files => localization repository ==> (L) translated source => "web" repository ==> (W) When there is a change in (D), it will call a job, and update pot files in (L) When there is a change in (L), translation platform will know and get updated When there is a change in translation platform, it will update content in (L) every day or night, content from (D) and (L) are used to generate content for (W), and publish it To be open: I offered to run a test using my own server as translation platform with Weblate and this is a personal choice for the development purpose. What we design is and should be translation platform agnostic. We have to discuss between translators if we want to use Weblate as a real world test or Zanata for the coming weeks. There is good and bad: Zanata will be stable but will require way more time for automation (I won't go into details here).

1 0

Re: Translations are coming!
by Brian (bex) Exelbierd 01 Oct '18

01 Oct '18

Adding trans(a)lists.fedoraproject.org On Thu, Sep 27, 2018 at 4:52 PM Adam Samalik <asamalik(a)redhat.com> wrote: > Hey everyone, > > I had some discussions about translations with a few people and this is > the result: > > We have a new epic [1] tracking the initial implementation. > > The English pipeline is quite straightforward — it takes the English > source and converts it into the English site. That already works today. > > Simplified view: `English source -> English site` > > The translation pipeline has a few more steps. First, we need to have a > script that converts the English sources to POT files [#114] which are used > for translations. These POT files need to be stored in a git repository > [#110] [#111] and will be consumed by a translation engine which pushes the > results back into the repo. To make it consumable for Antora, we need > another script that converts the resulting PO files into translated sources > [#115] and store them [#112] [#113] somewhere. Before the site can be > built, we also need to have a translated UI for each language that also has > a language switcher [#116] [#117]. The UI along with the translated sources > will be consumed by a build script [#119] that builds the final website. > > Simplified view: `English source -> POT files -> PO files -> translated > source -> translated site` > > Apart from these, we also need to have two new policies. One for adding > new content to the docs [#120] which need to ensure that the new content is > also being translated properly. The other one will be about introducing a > new language [#121] and will make sure that all the repositories are set up > and that the UI also supports this new language. > > Last thing is the "edit this page" button on translated sites. For that, > we probably need to have a page for each language explaining that the > content is created and edited in English, and how translations work and how > to contribute. And the "edit this page" link (with likely a different > wording) will point to that page. There are no cards for this, yet. > > So, we need places to store: > * POT + PO files for every language [#110] [#111] > * translated sources for every language [#112] [#113] > > We needs scripts for: > * Converting English sources to POT files [#114] > * Converting PO files to translated sources for every language [#115] > * Converting translated sources + translated UI to the translated site for > every language [#119] > > And we also need: > * Translated UI for every language [#116] [#117] > * Policy for adding new content to the docs that ensures adding it also to > translations [#120] > * Policy for introducing a new language [#121] > > > As you can see, the implementation will be "translation engine-agnostic" — > using POT and PO files. This way we can have some flexibility. > > I'll start working on it later this week. If you have any feedback or want > to help, let me know! > > Cheers! > Adam > > > > [1] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1 > [#110] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/110 > [#111] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/111 > [#112] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/112 > [#113] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/113 > [#114] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/114 > [#115] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/115 > [#116] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/116 > [#117] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/117 > [#118] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/118 > [#119] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/119 > [#120] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/120 > [#121] > https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/us/121 > > -- > > Adam Šamalík > --------------------------- > Software Engineer > Red Hat > > _______________________________________________ > docs mailing list -- docs(a)lists.fedoraproject.org > To unsubscribe send an email to docs-leave(a)lists.fedoraproject.org > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: > https://lists.fedoraproject.org/archives/list/docs@lists.fedoraproject.org > -- Brian (bex) Exelbierd | bexelbie(a)redhat.com | bex(a)pobox.com Fedora Community Action & Impact Coordinator @bexelbie | http://www.winglemeyer.org

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

trans October 2018