ABRT 翻译问题
by Christopher Meng
在 abrt 的 编辑-----》首选项----》Events里面,竟然出现了繁体中文,这是为什么?
*Yours sincerely,*
*Christopher Meng*
Got problems with Windows? - ReBoot
Got problems with Linux? - Be Root
Ambassador/Contributor of Fedora Project and many others.
http://cicku.me
11 years, 2 months
请问 trust down 怎么翻译?
by Zhenbo Li
Hi All
原话是“extend this chain of trust down into user binaries”,请问这里的 trust down 应该怎么理解?
另外,在 suggestion 里,允许扔下未翻译的词吗?
谢谢各位。
--
Together we’ll cry happy tears
See the nations turn their swords into plowshares
--<Heal the world>
11 years, 2 months
Fwd: Updated POTs for UEFI Secure Boot Guide
by Christopher Meng
前几天更新了后今天又更新了。
希望大家能够优先翻译一些热门文档。
感激不尽。
---------- 转发的消息 ----------
发件人:"Eric Christensen" <sparks(a)fedoraproject.org>
日期:2013-2-5 AM1:19
主题:Updated POTs for UEFI Secure Boot Guide
收件人: <trans(a)lists.fedoraproject.org>
抄送:"For participants of the Documentation Project" <
docs(a)lists.fedoraproject.org>, "Josh Bressers" <bressers(a)redhat.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I released version 18.2.3 of the Fedora UEFI Secure Boot Guide this
morning. Over the past week the guide has been greatly modified.
Lots of content has been added and we wanted to make sure this got out
there sooner than later.
I've updated the POTs in Transifex[0] and they are ready to be
translated. I'll try to monitor the progression of this work over the
next few days and will publish as soon as I see 100%. If I miss one
or you want to let me know when it is ready please hit me up at
sparks(a)fedoraproject.org.
[0] https://fedora.transifex.com/projects/p/fedora-uefi-secure-boot-guide/
Thanks!
- -- Eric
- --------------------------------------------------
Eric "Sparks" Christensen
Fedora Project | Red Hat
sparks(a)redhat.com - sparks(a)fedoraproject.org
097C 82C3 52DF C64A 50C2 E3A3 8076 ABDE 024B B3D1
- --------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJRD+2nAAoJEIB2q94CS7PRaiQP/2bOowK8ljvzNGzRnR7UqRB/
i0B4FYSr9DN+7IYCp1FNDM03X2TOJEcZ9VL8rjgrM7odYdm2U3LNQqlYVn3GCFBt
96MS4JnslDBMOgbfmxcVf7ToH47cQYo5/4J7Me9PQw8ufqYGZyLNDqNEqHeyjm52
Th7Vvw/f5yPHnbwcFF95BC/X1KO+w+ErkCU79E8MDgzePz3kOOPqMHH9PvK/D9jz
K+1nENptAgJsS2stae3mpADAqmGn7TuHmCn9Tht82ZHA5zFWK8ujL128lzTxe0GC
7bOndbWp8u8BwbuQrHJeXg+WVzWsvRQdkobZhwGeEF6q1Vy8zqFMSuvuhKT1pkVb
V3Vp27AtgiluC+7EC+McSp+ApQM8xK2KiDUJYibXtwLoue1QnDEqgI5U9qsVuqPH
+YIKclgtxCrxrj1nVwA0UnYZMWfiFlanSyvPJUFbrQ233AbqNfvA9QGkV0CPuJUO
9r2ywxpj/2lIAJQ1vhZiRcCRhjGBZ0mCtjy3MVNvnY5ozQXEVu38kOP6hiDnfbO1
gOkcvKLAcOMGhqK/Iz7kPmytkJl3ZYKUuzNTGKLch+DM6UEL/RJHzJFwpHe2XK/T
PO5aGIb81KttvWXl/LYj7KwQ0Fk+3ixdTbZSzRlW2XP2Pb8T4THhY5A1PwVbshJB
AGByIRKkY/CXFrwRc3WH
=kN3S
-----END PGP SIGNATURE-----
--
docs mailing list
docs(a)lists.fedoraproject.org
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/docs
11 years, 2 months
新人报道(colinluo)
by Smith Robert
Name:luo jiacheng
Location: 南昌,中国
Login: colinluo
Language: zh-cn,fr-fr
Profession or Student status:应届毕业生
About You:我最喜欢的大叔是让・雷诺,喜欢新鲜但是又有一点成熟的技术,大多数时候基本都是在尝鲜^-^
--
robert thomas smith
11 years, 2 months
Fwd: Installation Guide and Installation Quick Start Guide ready for translation
by Christopher Meng
---------- 转发的消息 ----------
发件人:"Jack Reed" <jreed(a)redhat.com>
日期:2013-2-1 PM12:30
主题:Installation Guide and Installation Quick Start Guide ready for
translation
收件人:"Fedora Translation Project List" <trans(a)lists.fedoraproject.org>
抄送:
Hi everyone,
The Installation Guide and Installation Quick Start Guide are now ready for
translation for Fedora 18.
The twist - and the reason for the regrettable delay in making the
translation files available - is that for this release the two guides have
been consolidated into one Zanata project. This is because the Installation
Quick Start Guide is mostly a heavily abbreviated version of the
Installation Guide, with only a small amount of original content. So to
save you translating the same strings twice in different projects, I've
combined them into one git repo and therefore one translation project.
The f18 Zanata project contains all transferable po files from the f17
translations of *both* guides, so your work can simply continue from there.
However, the content for the F18 Quick Start Guide is almost completely new
due to the redesign of the installer for this release. Nonetheless, I have
preserved po files unique to the Quick Start Guide that do not need to be
updated for F18, so those select strings will not need to be translated
again.
The only quirk is that the files required to generate the Quick Start Guide
cannot be marked as such within the Zanata project. Ideally, these files
should be translated first so the Quick Start Guide can be released at the
earliest opportunity.
So I've created a wiki page that lists these files:
https://fedoraproject.org/**wiki/Installation_Quick_Start_**Guide_files<https://fedoraproject.org/wiki/Installation_Quick_Start_Guide_files>
The link to the Zanata project can be found there too. (The entries for the
guides in the Docs Project guides table [1] now link to this page instead
of straight to the Zanata project.)
If you could work from this list and then let me, trans-list, or docs-list
know when these files are translated, it would be much appreciated. I can
then publish the Quick Start Guide in your language. If you choose to
proceed with the remaining files, you will effectively then be translating
the Installation Guide.
Thanks for your patience, and I hope this consolidation makes the
installation guides a slightly less daunting translation prospect. :)
And thank you for your continuing hard work and dedication in broadening
the reach of these resources, which will likely be in even more demand due
to the redesigned installer.
Please let me know if you have any questions or concerns.
All the best,
Jack
[1] https://fedoraproject.org/**wiki/Docs_Project_guides_table<https://fedoraproject.org/wiki/Docs_Project_guides_table>
--
Jack Reed
Content Author
Engineering Content Services
Red Hat Asia Pacific
Brisbane, Australia
Phone: +617 3514 8184
--
trans mailing list
trans(a)lists.fedoraproject.org
https://admin.fedoraproject.**org/mailman/listinfo/trans<https://admin.fedoraproject.org/mailman/listinfo/trans>
11 years, 2 months
Fwd: New Websites translation workflow
by Tiansworld
请仔细关注第 5 条,即考虑采用 transifex 的审阅(review)功能。在 Fedora
网站翻译新工作流程中,打算仅使用审阅后的翻译做为网站翻译。考虑到目前我们对审阅功能使用有限,website
翻译也没有审阅过多少条。而如果同意这么做的话,我们要把翻译一条一条的标为已审阅。所以我暂时没有同意第 5 条。
其它部分也希望仔细看看。原文请看 trans 翻译列表。
---------- Forwarded message ----------
From: Kévin Raymond <shaiton(a)fedoraproject.org>
Date: Thu, Jan 31, 2013 at 10:18 PM
Subject: New Websites translation workflow
To: trans <trans(a)lists.fedoraproject.org>
Hi there,
I would like to introduce you some changes that I am going to do on the
Websites, that will change a bit the way your are managing the translations.
It is not fixed yet, please give me your thoughts if you think that we need to
improve some parts, remove others or just stick with my proposal.
Don't be afraid, I won't introduce major changes! Oh wait, in fact I will (see
point 5 if you don't want to read this email completly!)
Here are the ideas, with an approximated schedule:
1. We have been pulling all translations twice hourly for years now from
transifex.net (twice because we use staging). That is a slow process, and not
really needed.
Therefore we have started to only pull the translations daily, once (shared
between stg and prod). This is effective only on staging actually, and will move
to production soon. It is transparent on your side, but the fact that we pull
the translations only once a day. You've been warned, now when you translate on
transifex.net, it will only appear on the websites the day after.
This could be moved to daily during string freeze, or a week before the
release. Please tell us if it's needed (I don't think it's really needed but
give your voice).
Of course, if you've made a terrible mistake and something is bad on your
translation, you'll need to wait untill the next day. This is bad. Try to think
if it could happen. But you should really proofread your translations, and I am
sure that you will never get this problem :)
The POs files on the websites repository won't be used at build time. We get the
POs directly from Transifex from inside our infrastructure.
I need your help to check that it is working as it should. Please, translate on
master, and proofread on stg.fedoraproject.org, spins.stg.fedoraproject.org,
start.stg.fedoraproject.org and so on. I would like to be sure that with new
POs it still work. (I can check it but your help is appreciated).
(1.) Expected change by the 13th of Feb
2. Because the POs on the git repo won't be used at build time, they are
probably going to be removed from the repo. Since Transifex keep an history and
the push access are spread between teams, there should not be any really bad
situation (like wrong language overriding). We could keep them here for the
websites team, as we need to test some language build, but I think we will
remove them shortly (as I have seen some commit on Transifex to enable pulling
without being logged in).
(2.) Expected change by the 13th of March
3. Our translation process at release time is not the best. We used to create
alpha, beta and master branches for some websites (mainly fpo and spins.fpo) to
let you translate and review the websites on stg before the release. To do this,
we copyied the translations from the previous branch (master to alpha, alpha to
beta and then beta to master) but doing this:
* The maintainer get the translations credits by Transifex.
* The string history is lost.
* We are all lost because only people on the infra team could know where we are
pulling translations, and on which branch we build the websites.
I already spoke about a new process months ago. Here is a formal introduction:
* We will use only one Transifex resource per website.
* Once we decide to prepare the websites for next release (alpha, beta, finale),
we will freeze the POs on prod (let's take as example alpha, if we are ready
to move to beta) and push the upcoming POT to the current release. You'll then
be able to translate the "new" website on the usual resource. You'll keep your
translation history, the credits etc.
* At the release date (for example for beta), we will just enable again pulling
the POs which would be up to date.
This does not change to much to you as we used to lock the translations during
the freeze, to avoid lost of translations when moved to the next stage (i.e
beta).
Of course, we always try to avoid string freeze break, but again, we depend on
marketing, docs, design, SIGs.. At every release we are making our websites
stronger, which leads to more quality for you.
(3.) Expected change for the F19 Alpha release
4. To let you work on new languages or new websites without loosing the visitors
with a too light translation, we will start pulling only PO files translated at
least with 30% of completion. Please tell me if 30% is too small, 50% could be
fine but I am not sure if we want to make this websites dependant (like 50% of
start.fpo Vs 50% of spins.fedoraproject.org).
With this, a visitor won't be able to select the foo language is the website is
not translated at more than 30% for this specific language.
This is valide for production and staging, we won't be able to separate those
because of the point 1. explained above.
(4.) Expected change by the 13th of Feb
5. There has been a good unknown Transifex feature for months now. The ability
to review translations. I still don't like the way it is implemented: the
maitainer (devs) has to choose for the translator the quality desired. No, it
should come from the translation team. But let move this discussion on an other
thread, later.
Here, on the websites team, we are going to pull reviewed translations only.
That is going to be a *huge* change for you. Therefore, we can probably enable
this feature for specific teams only. I don't know yet how this would be set.
Please every coordinators, tell me if this is something that you don't want for
your team. The downside of this change is the need for your team to mark as
reviewed all your translations.
It could have changed (I did the feature request 3 or 4 months ago)− and don't
ask me which ticket is it, I just can't track them all on their 3 different
trackers) but here is how it works:
* to review a string, you need to do it through the online translation tool
(Lotte) only. You can't authomatize that with the transifex client.
* this is by-string or by-page process. You can't mark as review the whole
resource or project. I let you imagine how to mark as reviewed a project with
several rersources made of thousand of strings... Thanks to Transifex, the
hot feature is a pain to start with. That's mainly why we haven't used that
before, but I got the request to do so and it will add more quality to your
translations. I strongly hope the made something to help us starting.
* only reviewers can review strings. So the language coordinators have to select
some reviewers. A reviewer is a translator that have one more power, the
hability to mark strings as reviewed. You can define them all as reviewers of
course.
(5.) Expected change for the F19 Alpha release. But it really depends if we need
to do this per language, and about your opinion. This is really the major change
for you and we won't move forward on this topic if you don't want this for your
team. That's why I need you to let me know if you don't want this. Yeah, if you
don't reply for your team because you haven't read about this I will assume that
you agreed :) We will choose the best solution for you! (I shall probably send
a reminder..)
Hope you are going to find those point nice, tell me if it's not clear or if you
have better ideas, or if I am missing something.
--
Kévin Raymond
(Shaiton)
--
trans mailing list
trans(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/trans
--
Regards,
Tiansworld
Fedora Project Contributor
11 years, 2 months