Merging transifex.net duplicated teams
by Kévin Raymond
Hi there,
Since our migration to transifex.net, some teams have lost their
translations because a new team was created (thanks to language mapping
in transifex.net).
There are still some project that need to be merged.
I've written a script[1] used to parse all guides at TXN, and print the
language code which have translations but are not associated to any
teams.
Please find attached the results.
Limitations:
- it was against the fedora-docs release only, not against
all docs! I could have used an other script for that.
I have it around but I would prefer our guides to be on
the fedora-docs release. This refers to[3].
Should I add all in this fedora-docs release? I think so, but
we never finished that…
Should I add all in this fedora-docs release? I think so, but
we never finished that…
There could be an other way, but I think that I've more than needed.
This list should be checked with the Misha's one[2].
we really need the maintainers to act!
Some guides are completly translated but using the wrong language code,
we can't publish nor re-use translations.
I think we need a clear list of which l_code have to be merged in which
one, the thread [2] should helps.
@maintainers, please ask if you need help for that!
[1] https://gitorious.org/tiny-scripts/transifex/trees/master/check_teams
[2] http://lists.fedoraproject.org/pipermail/docs/2011-August/013611.html
[3] http://lists.fedoraproject.org/pipermail/docs/2012-March/014116.html
--
Kévin Raymond
(Shaiton)
11 years, 10 months
Problem when trying to publish zh_TW technical notes
by Tiansworld
Hello guys,
There is a problem when I try to publish zh_TW technical notes by using
publican. Request is at here[1].
The error output is:
###
...
WARNING: Message missing from PO file, consider updating your POT and PO
files.
"13"
PO file 'zh-TW/Development-Libraries-PHP.po' not found! Using base XML!
Merging zh-TW/Development-Libraries.po >>
en-US/Development-Libraries.xml ->
tmp/zh-TW/xml_tmp//Development-Libraries.xml
no element found at line 1, column 0, byte 0:
^
at /usr/lib64/perl5/vendor_perl/XML/Parser.pm line 187
###
My procedure was as follows:
1. git clone git://git.fedorahosted.org/docs/technical-notes.git #ok
2. tx init && tx set --auto-remote
https://fedora.transifex.net/projects/p/fedora-technical-notes/ #ok
3. tx pull -l zh_TW #ok
4. publican build --embedtoc --publish --formats
epub,html,html-single,pdf --langs zh-TW #error output
I checked there is not Development-Libraries-PHP.po available under
zh-TW but that xml file exists in en-US directory.
Also there are only 58 xml files in en-US directory, but the translation
po files are 72. Seems the git repository is too old.
Could anyone help me?
Many thanks.
[1] https://bugzilla.redhat.com/show_bug.cgi?id=817969
--
Regards,
Tiansworld
Fedora Project Contributor
11 years, 10 months
[Bug 823654] New: Wrong FreeIPA Guide for F16
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=823654
Bug ID: 823654
QA Contact: docs(a)lists.fedoraproject.org
Severity: medium
Version: devel
Priority: unspecified
CC: eric(a)christensenplace.us, oglesbyzm(a)gmail.com,
stickster(a)gmail.com
Assignee: nobody(a)fedoraproject.org
Summary: Wrong FreeIPA Guide for F16
Regression: ---
Story Points: ---
Classification: Fedora
OS: Linux
Reporter: cevich(a)redhat.com
Type: Bug
Documentation: ---
Hardware: All
Mount Type: ---
Status: NEW
Component: docs-requests
Product: Fedora Documentation
Description of problem:
Fedora 16 uses FreeIPA 2.1.x, and the FreeIPA.org site correcty points it's doc
link at the 2,1,3 fedora documentation. However, the FreeIPA Guide listed under
Fedora 16 is for version 2.2.x which isn't available, though is slated for
Fedora 17 (I believe).
Version-Release number of selected component (if applicable):
Fedora 16 Documentation
How reproducible:
Very
Steps to Reproduce:
1. https://docs.fedoraproject.org/en-US/Fedora/16/html/FreeIPA_Guide/index.html
2. https://docs.fedoraproject.org/en-US/Fedora/15/html/FreeIPA_Guide/index.html
Actual results:
Fedora 16 users reference documentation for a much newer version of FreeIPA.
Expected results:
Fedora 16 users reference documentation relevant to availabe FreeIPA version.
Additional info:
I don't believe there is much different between FreeIPA 2.1.3 and 2.1.4 which
currently ships, it's probably fine to just keep referencing the 2.1.3 docs for
Fedora 16.
--
You are receiving this mail because:
You are the QA Contact for the bug.
11 years, 10 months
Docs Project Meeting Minutes 25 June 2012
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2012-06-25/fedora_docs.20...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2012-06-25/fedora_docs.20...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2012-06-25/fedora_docs.20...
===================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda:
http://fedoraproject.org/wiki/Docs_Project_meetings
===================================================================================================
Meeting started by Sparks at 14:00:08 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2012-06-25/fedora_docs.20...
.
Meeting summary
- ---------------
* Roll Call (Sparks, 14:00:23)
* Follow up on last week's action items (Sparks, 14:05:03)
* Using koji to publish docs.fp.o - Sparks (Sparks, 14:06:20)
* List discussion
https://lists.fedoraproject.org/pipermail/docs/2012-May/014324.html
(Sparks, 14:06:29)
* LINK: https://fedoraproject.org/wiki/Automating_publishing
(Sparks, 14:06:34)
* Publish man pages (Sparks, 14:10:24)
* LINK: https://bugzilla.redhat.com/show_bug.cgi?id=828669 (Sparks,
14:10:38)
* BZ 828669 (Sparks, 14:10:39)
* QA recap (Sparks, 14:12:55)
* LINK: https://fedoraproject.org/wiki/Docs_QA_Procedure (Sparks,
14:13:02)
* Open Help Conference (Sparks, 14:14:51)
* LINK: http://openhelpconference.com (Sparks, 14:15:02)
* Open Help Conference is Aug 11-15 in Cincinnati, OH (Sparks,
14:15:02)
* Outstanding BZ Tickets (Sparks, 14:25:38)
* LINK: http://tinyurl.com/lbrq84 (Sparks, 14:25:50)
* Open floor discussion (Sparks, 14:26:23)
Meeting ended at 14:30:38 UTC.
Action Items
- ------------
Action Items, by person
- -----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
- ---------------------------
* Sparks (50)
* jjmcd (12)
* fnadge (10)
* lnovich (5)
* zodbot (4)
* suehle (2)
* sheap (2)
* sgordon (1)
* mprpic (1)
* jhradilek (1)
* shaiton (1)
* pkovar (1)
* jsmith (1)
* Capesteve (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP6HaeAAoJEIB2q94CS7PR6U4P/iMj8Ie1S3Lw+hn2HlrOvuy4
dvTTlo1OOrzE90L6WifDQsfcPpUHqjKL9BNFfWs+Rw2+RHyrg/R7hKO4AzgTIv83
VFexzBa8eWnFYGtzUqn3DnwVebkoRoj1yesL+sqDMrXw6g3xODYewdkuviisD6Iu
tcjHtbsLCfUtd9DYeDMG+mazqUSGDqPK2gFWUlk9Xdn6KRO0uGt9xVdz/dNveE1Q
RfT8rUITSGvfN5MT6c6AJkLo/iF8ddxbQ8z6xxlXvsd8+IzhPbkptCPfxPC5M84u
jpNFhCRXWGq7deZYR0dt5hGGidLwgLtdoBLZ6DjjUr8iB1dbEuyDZxRyrr54lmlD
ijoxj1YTA+Z1W03OV9XfKz3jjjhry/irzhaYlbOiswpME/zf29XglbcFf0Dgd1wH
cA6BH8L6p6QZ5wI2xPXLEkKSdHunZPNMlTINz5eTEUz+IOrHK3TiDYJJAGEqK5wa
GosE1D1pT3Qg/wtfT2h4C9ti6/So3WZ8tuui4ol52YXDkCkr+21njcExi9MIEVi+
ZglfOhvmP5L/jwUAZ3MH5JA9jN/dKuDkvwC0Lzr+fY/YOJBA/yWz2rMnahaxupqJ
orVbzD3BsTcWdeFFiCabTG41TZfE3wnfJiut9KOtOcKSVzNP7wnsIw+shbjFIO+3
IaiTk/P0KJValbM1iAoH
=7vg7
-----END PGP SIGNATURE-----
11 years, 10 months
Python wiki editing help (mwclient)
by Ankur Sinha
Hi folks,
I'm trying to write a simple python script to generate agenda pages for
various team meetings. The initial version is here[1]. There's still
work to be done to make it more convenient to use, even more generic so
that all teams can use it.
Now, using mwclient, I cannot add external links to the pages (such as
timeanddate.com links, or the {{fpchat|fedora-channel}} template link),
since it wants me to solve the captcha. Would anyone know if there's a
way of retrieving the captcha question and answering it using python so
that external links can be added? I wouldn't want to circumvent the
captcha, since it's there to prevent spamming (mostly via bots and
scripts :D), but I'd be glad if I could solve the captcha and post the
page with external links.
Most of this[2] wiki page is generated by the script. I've made changes
later.
It isn't a big deal: I can always add stuff a little malformed to get
around the captcha and then correct the page manually. I was just
wondering if it was possible to interact with the captcha.
[1]
https://gitorious.org/miscellaneous-sanjayankur31/miscellaneous-sanjayank...
[2] https://fedoraproject.org/wiki/Meeting:APAC_Ambassadors_2012-07-07
--
Thanks,
Warm regards,
Ankur: "FranciscoD"
Please only print if necessary.
Looking to contribute to Fedora? Look here: https://fedoraproject.org/wiki/Fedora_Join_SIG
http://fedoraproject.org/wiki/User:Ankursinha
http://dodoincfedora.wordpress.com/
11 years, 10 months
Fedora Docs Meeting Reminder
by Ben Cotton
This is an automated message to remind you that we will be meeting at 1400 UTC in #fedora-meeting. Unless we've previously agreed that we will not be meeting today.
11 years, 10 months
Publican + Koji = Win
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Intro:
The web git repo is getting unmanageably large. We're tossing around
several GB across the Internet and not only does that take time but it
also takes space. The 'fix' for this problem was pretty simple.
Publican can create packages (SRPM) and submit those packages to Koji
where they can be added to a repository where our website
(https://docs.fedoraproject.org) can then do a yum install and add
those documents to the website. Never again will you have to sync
several GB of data just to publish to the web.
Where we are now:
A ticket has been opened with Rel-Eng
(https://fedorahosted.org/rel-eng/ticket/5214) to add a tag to Koji to
support our documents. There are also some updates to Publican that
need to be pushed as there are older versions being utilized in EL5
and EL6. Right now we are waiting for Rel-Eng to finish getting F17
for ARM sorted out.
Rudi is working on moving this forward and I'll be following up with
him on this as time moves forward.
- -Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP4w5jAAoJEIB2q94CS7PR03AP/0eRIeOP5ljCJYdiHzm1bsrk
vmTbTyDPlzLHMiWE+IaUA0aUBp3R7mfHE5PrmdL1kES1pdR3UaS/cDc3YefIkOIE
kBFR7vAeNMBB/fgZIjFC+odEf0odwxKgo730kYTledegDU/X0C9bKtR76FiN54uq
WegnkCJgLzkgaoNBnttBz1n/TyZXamLrYwkBLUfQh/WixylOmQSFkd8jVqg3bSx9
URM+3tsrGcfH4ieNWjWYlUiHEQO99Bu4kWMZZRCK4NczaEQAviAzC87K+4N9UCrJ
Ns6WKom1iyogKTW+Y52tEkAILWvOvgC2BU8R2qkLjGX6o9jDUpeT4GbleuFshIGh
AcqSa6olftgmze9++bUNBqQ+IujSaHyBT8zCdmAVOYZb9tjGMthZP0Kj9x5Mu7Wk
m/75aquqnJxiW2aSo4LWn6dhi2JMSUINWWKCnT5tQQ1yn6Lrsc3IVXHLn3fCUNd8
7Iq9zxOygDhpLFIGCsfcprWGSGUk7j5i/eqL2fg0L1IZTHeF5PNeqwFdlMK2sqkK
+ohuRMHtpQGENKgD/89FzEWbV7sRnTx/SbRaQtQSY/up6pz1HwwoI8NgulnPHPRK
p4ColR6JPmG5rPBx16ySG4jSSm0mt5Ht2mXdKCqXCGgrHsJ1rZyB+bI/vmzDe/fU
cPzYtaSgDAQDX7VVpVfv
=l0Sh
-----END PGP SIGNATURE-----
11 years, 10 months
Updated pot files for the Security Guide
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In the better late than never category, I finally got around to
branching the Security Guide for F17. There were a few additions to
the guide since the previous submission which knocked the translations
back two points.
The Dutch, Italian, and Japanese translations are now at 98% and the
Spanish translations is now at 86%.
I'll be watching for translation updates over the next few days and
will publish the translations that I see as complete.
Thanks,
Eric "Sparks"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJP49cIAAoJEIB2q94CS7PR8G8QAOYd+bd7E7R1ihp5u6VH+hjU
3hmHkpnAnpoLHbxxEJOAp0S690qwu5DifO3z9eQcs80wr66ZLaiB34plCvKBvsrP
opgXvxQfvqXYUEEW+O9rtC5mlw7+Hx3IHMoB6XSeTcAyp1PCj9lXhwInlKYerLa2
DzFTt6i1Wf5sFCn++Pb3xaKK3rdDnUijaGBbAtDlGqILc+XURtBrsp/T/GzRCA8J
J4fnquHMR5cECBzNMM1vNZNCMdMVlWuRUmCClkCPOA96Su47RAL+LyGyF/V7MOR0
in2HAUYsYkuRitIiq52+wE1LX54G+ao+hO/IC6r5NucLxerO89YAvKE+jgBN1/JD
t+xskXwuzTwfNoQXm7w55g7JurcffsbqT/YPq/W0LRQas5hr5XphhK7+gRUIqc0U
WeppSaNVVvf8iCW4bfvt6Rl4NpL7KRvve+NjCGM73V09oaT69whlcaNzi4xKhIAD
Lyn694EaB9kooevWAyygh+SfNfgdVLx08/6rkGPgCmxz/ZMqaJIyMqR4jhPBRRVi
tlyHfGvvg/wOZXur8qVq9oAofs8w3ofmzRkuxbjerX1Hbsz3Al1xfUU9bGgSjT5I
W8I90SLvMccAJUt3cMxRRNQ4z7nq44a6b7+k8Zu5Y17R6gNInzVZB2Cr1asVl5O0
VZN//uWAZZdasRl2PSGT
=GK/a
-----END PGP SIGNATURE-----
11 years, 10 months
Requesting docs & docs-writers group memberships
by Dayle Parker
Hello,
Requesting membership for these Fedora Docs groups please:
1) docs
2) docs-writers
As well, I've had to create a new GPG key, so please disregard my
earlier key sent with my self-introduction and replace with:
[dayle@localhost ~]$ gpg --fingerprint dayleparker(a)redhat.com
pub 2048R/F4993692 2012-06-19 [expires: 2014-06-19]
Key fingerprint = BA82 DE33 DFAF 47FE 1E86 085B C85B C873 F499 3692
uid Dayle Parker <dayleparker(a)redhat.com>
sub 2048R/70DE277B 2012-06-19 [expires: 2014-06-19]
Thank you very much,
Dayle Parker
--------
Content Author
Engineering Content Services
Red Hat Asia Pacific -- Brisbane, Australia
11 years, 10 months
Self-Introduction: Inna Kabanova
by Inna Kabanova
Hi all!
My name is Inna Kabanova and I'm a member of the Russian Fedora L10N Team. I would like to become a docs publisher for Russian team. I talked to Daniel Cabrera about publication process and he gave me some details about publishing. I've tried to repeat all the steps by myself using the local website and now I know how to do it.
As far as I understand, I should join docs-publishers FAS group but it is invite only. Could anybody add me?
What should I do next?
Thanks in advance.
My FAS name: mamasun
My wiki-page: https://fedoraproject.org/wiki/User:Mamasun
----
pub 1024D/2C192FDB 2009-08-29
Key fingerprint = 3DA1 9B51 2A71 3BB7 6DEE DF2F D9C5 4E4F 2C19 2FDB
uid Inna Kabanova <ikabanova(a)russianfedora.ru>
sub 2048g/490B260A 2009-08-29
--
Best regards,
Inna Kabanova / Russian Fedora Team
ru.fedoracommunity.org
11 years, 10 months
