wkhtmltopdf
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
If you haven't been paying attention to the Publican list recently then you may not have seen that Publican 3 is now out. IIRC it has only been pushed to users of RHEL for now. This is a major accomplishment for the Publican team and we'll begin reaping the benefits as soon as we can figure out the web site of the house.
One piece of this puzzle is the ability to replace fop with wkhtmltopdf as the engine to create PDFs. Unfortunately there is a problem with wkhtmltopdf that prevents us from using it in Fedora. This means that for the time being we'll have to continue to use fop but that isn't a great solution. I can't recall all the problems with fop, off hand, but I hear that wkhtmltopdf is both better and worse.
I'm hoping that Rudi will give us a rundown on the issues with wkhtmltopdf and what needs to happen to get it into Fedora. I'll volunteer to help package it if we know the what the issues are and can get a game plan around fixing them.
- -Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQkdGKAAoJEIB2q94CS7PR91MP/3jU+oBUL85o2SI+ejLWluH0
KPer+XM8ZYetFabpOgris8HMvXTZx5OtQxk09WdyGNaSWlgJbxnZ6Exq1vtkkJ+q
6EeIBgMdxVmgwMQ1mlYrhwBBcfZWT8DA3Q4bNf8h46KDLK5054uryggafd1JaVlq
m/SWq74Bb2AQyV6BDwfufSZ1p3wi6zKBLpxVHXC/Gpx4WNnidIer5XlhB7u3sOri
mpwIohJ55ArSPjCJXJwUoFbrWpUAw1E27Ls6gYH/NVoh+SC4ge8CfU/v0iFyhl/L
O7HPX+mAupF21xajG4yzCbCOvKpcI44LEX0lJeMBZEo4BSfbInMtKMTyjxFZ+ZJn
JbePqLt6wJrkyTI/XwxQcRXmk0gv4eLxegi41RpPosp9351PlsiBm5sc4AQNB89b
3nY6w++iZvwM3tFHr/pOd2nXRNtibklarRTNmdDc75PQ9QpqHXC87bpfmI05uvkm
79ygCNLBXHiH6uJsDQKQ7wHhc+imiqqHFAh7M0FeEwd3WYkHcmi/rOXLFCSt6+b7
qR5jBLKOs+hSzjg3ARTAwqIT2GSVuBF2t+4MtBJnjzkTpwHOI8zhPoxPj0L3sJUR
p/XHXznI6Ig7Fb4jWRWO6I2rrbhfi8k6znbdj3Mve91YDDkQ131qjqduZcfKlECF
bZWkhotXTrrjLlKsRy53
=3J2K
-----END PGP SIGNATURE-----
11 years, 5 months
Beta documentation: upgrades
by Adam Williamson
Hey, folks. I just wanted to check in and see if someone's on top of
documenting the upgrade process for Beta, as it's still somewhat manual.
I don't believe it's going to be as simple as 'yum install fedup; fedup'
- it'll at least involve feeding an explicit URL to fedup.
We have a test case that documents the current procedure:
https://fedoraproject.org/wiki/QA:Testcase_upgrade_fedup_cli_previous_des...
I believe the target URL will change for the public release, but the
procedure I think will stay more or less the same.
Does someone want to co-ordinate with wwoods and tflink (who know the
most about fedup, I think) to make sure this is documented in the Beta
relnotes or whatever? Thanks!
--
Adam Williamson
Fedora QA Community Monkey
IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora
http://www.happyassassin.net
11 years, 5 months
Docs project meeting summary 26 Nov 2012
by Eric Christensen
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Minutes: http://meetbot.fedoraproject.org/fedora-meeting/2012-11-26/fedora_docs.20...
Minutes (text): http://meetbot.fedoraproject.org/fedora-meeting/2012-11-26/fedora_docs.20...
Log: http://meetbot.fedoraproject.org/fedora-meeting/2012-11-26/fedora_docs.20...
====================================================================================================
#fedora-meeting: Docs Project Meeting - Agenda: https://fedoraproject.org/wiki/Docs_Project_meetings
====================================================================================================
Meeting started by Sparks at 14:01:44 UTC. The full logs are available
at
http://meetbot.fedoraproject.org/fedora-meeting/2012-11-26/fedora_docs.20...
.
Meeting summary
- ---------------
* Roll Call (Sparks, 14:01:52)
* Follow up on last week's action items (Sparks, 14:07:18)
* ACTION: bcotton to finish RN RPM (Sparks, 14:07:39)
* ACTION: bcotton to add BZ 865922/875433 to Release Notes (Sparks,
14:08:09)
* ACTION: randomuser and dan408 to improve MATE blurb in RNs (Sparks,
14:08:41)
* Fedora 18 schedule (Sparks, 14:09:07)
* LINK:
http://jreznik.fedorapeople.org/schedules/f-18/f-18-docs-tasks.html
(Sparks, 14:09:19)
* Beta is scheduled to be released 27 November (Sparks, 14:09:29)
* F18 final is scheduled for 8 Jan (Sparks, 14:09:42)
* Release Notes (Sparks, 14:10:49)
* if RPM not done jjmcd will be available to help (jjmcd, 14:11:40)
* Outstanding BZ Tickets (Sparks, 14:15:00)
* ACTION: zoglesby to ask about fedup info in release notes on
docs-list (zoglesby, 14:15:01)
* LINK: http://tinyurl.com/lbrq84 (Sparks, 14:15:07)
* 117 bugs open (Sparks, 14:15:27)
* Open floor discussion (Sparks, 14:23:04)
Meeting ended at 14:28:52 UTC.
Action Items
- ------------
* bcotton to finish RN RPM
* bcotton to add BZ 865922/875433 to Release Notes
* randomuser and dan408 to improve MATE blurb in RNs
* zoglesby to ask about fedup info in release notes on docs-list
Action Items, by person
- -----------------------
* zoglesby
* zoglesby to ask about fedup info in release notes on docs-list
* **UNASSIGNED**
* bcotton to finish RN RPM
* bcotton to add BZ 865922/875433 to Release Notes
* randomuser and dan408 to improve MATE blurb in RNs
People Present (lines said)
- ---------------------------
* Sparks (41)
* zoglesby (5)
* jjmcd (4)
* zodbot (4)
* jhradilek (1)
Generated by `MeetBot`_ 0.1.4
.. _`MeetBot`: http://wiki.debian.org/MeetBot
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBAgAGBQJQs30CAAoJEIB2q94CS7PRrOEQAKL1U9osjYtasfxjgIRodt+S
zGsJ4KGEGMRMAgBSB4cHzoICz5XEVqYet7TbctHKoQjlczFBZB5oOPQGYbXj/H6b
G5ygujzoNCdJVAC9kQQTgsrDT8ON0LPJWxiEs+Ai8B8+ZouCZlhAB1N7igyLMSr9
S7CC8oG5+iZGAaCr1BwuF99oAUy1SgMmczIRSh0CW7GfvT4I+ZRj0xPrOTaPSUzR
IlwJ+WV7ixaeXpLEGV6FZXUSAWE2La69GdepeDs2h7PEjoRIXzCVJL7KChmXdpmJ
/PU2qb/gjtOc4nMtRpESE5DIWyPbwlvSHMvDvnaI0WvoQH6QIyzSJRXHPKN8NfWG
Aimn95U8NqQF6H+4ZpURSo8dzbJfijPcAdz/FnblXKcTagmwisYwttxTI07+nleA
hZA0rMNMF/7b0BVLsMO73tBarHY4AzW+2Cav/rnnec8FRxBE5R50cMTj5VluVx/s
aDDIZsL9ppUOdxZiOjo/VB1MKzcJtAsMBnADE52VBBSqnlDyO2Ng9K+FUoet+4Lf
IkkXhx4G1a+QQXg7d5GIrEFjGw9J76O+jhlECbTnTJsVlGCo8kD2W4ne3rMGBd7W
RAicM6hiPm5Heqxavh/NJk2YFHCciF2oKS/wxrWL29olF7z7I1E8g4SSMU+EYTa9
xpR44Owh/MzF7aE/6cbo
=lxh3
-----END PGP SIGNATURE-----
11 years, 5 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, 5 months
Release Notes: The content within some tags is missed from po-files
by Inna Kabanova
Hi there,
The issue is that I couldn't find certain parts of some strings from the original English version of RN in the po-files. And since the string from po-file and string from the source xml-file are different, the source string is included in the final document. So we have no chance to translate them.
I've found 3 strings where it occurs. I've opened the Bugzilla ticket [876506] and described them in it. In short:
-- <productname> tag dissapears from <ulink> tag (File_Systems.po)
-- <productname> tag dissapears from <emphasis> tag (Desktop.po)
-- <ulink> tag with <orgname> tag in it wholly dissapears with it's content (Desktop.po)
Translators, did anybody face with the same problem? I can't understand why it happens.
[876506] - https://bugzilla.redhat.com/show_bug.cgi?id=876506
--
Best regards,
Inna Kabanova / Russian Fedora Team
ru.fedoracommunity.org
11 years, 5 months
Docs Meeting Summary -- 19 November 2012
by Ben Cotton
Meeting summary
---------------
* Roll Call (bcotton, 14:00:21)
* Reminder: participants are encouraged to make liberal use of #info
#link and #help (bcotton, 14:05:15)
* Follow up on last week's action items (bcotton, 14:05:44)
* ACTION: bcotton to finish RN RPM (bcotton, 14:06:10)
* ACTION: bcotton to add BZ 865922/875433 to Release Notes (bcotton,
14:06:19)
* ACTION: randomuser and dan408 to improve MATE blurb in RNs
(bcotton, 14:08:02)
* Fedora 18 schedule (bcotton, 14:08:17)
* LINK:
http://jreznik.fedorapeople.org/schedules/f-18/f-18-docs-tasks.html
(bcotton, 14:08:26)
* Beta is scheduled to be released 27 November (bcotton, 14:09:24)
* F 18 final is scheduled for 8 Jan (bcotton, 14:09:30)
* Release Notes (bcotton, 14:22:18)
* Outstanding BZ Tickets (bcotton, 14:24:46)
* LINK: http://tinyurl.com/lbrq84 (bcotton, 14:24:53)
* Open floor discussion (bcotton, 14:26:57)
Meeting ended at 14:30:45 UTC.
Action Items
------------
* bcotton to finish RN RPM
* bcotton to add BZ 865922/875433 to Release Notes
* randomuser and dan408 to improve MATE blurb in RNs
Action Items, by person
-----------------------
* bcotton
* bcotton to finish RN RPM
* bcotton to add BZ 865922/875433 to Release Notes
* randomuser
* randomuser and dan408 to improve MATE blurb in RNs
People Present (lines said)
---------------------------
* bcotton (49)
* lnovich (16)
* Sparks (7)
* jjmcd (6)
* zodbot (4)
* zoglesby (3)
* Capesteve (2)
Minutes:
http://meetbot.fedoraproject.org/fedora-meeting/2012-11-19/fedora_docs.20...
Minutes (text):
http://meetbot.fedoraproject.org/fedora-meeting/2012-11-19/fedora_docs.20...
Log:
http://meetbot.fedoraproject.org/fedora-meeting/2012-11-19/fedora_docs.20...
--
Ben Cotton
Fedora Docs Leader
11 years, 5 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, 5 months
Re: Release Notes ready for translation
by Kévin Raymond
> I'm not sure what's happening here. Just now, I ran a `publican
> update_pot` and `tx push -s`, as in
> http://docs.fedoraproject.org/en-US/Fedora_Draft_Documentation/0.1/html/D... . Glancing at the project on transifex, I see that a number of resources are missing F18 strings.
>
> There has to be something I'm missing here. My Installation.pot is for
> F18. Transifex doesn't show *any* strings relevant to F18 under
> Installation. Can someone help me straighten this out?
Cc-ing to docs as I see what is happening here.
We used to do a tx push -s. Hey, what happens if we don't override an old file,
that is not existing on the current branch? It just stay like that on Transifex.
After a quick check with the Transifex team, if we delete a ressource, the TM
won't be affected.
Here is the best workflow IMHO:
At each new release do:
- Delete all ressources from `Fedora Release Notes'
- Upload the new POT (tx push -s)
- Check on the `Fedora Release Notes' project management under Transifex that
`Fill up resources from TM' is checked in order to have transifex filling the
translation memories from older releases.
- Let the Fedora Project Hub maintainers know that they need to update the
`Fedora Documentation' release. Maintainers are written at
fedora.transifex.com. They need to add every ressources to this release.
Manually...
- Finally, notice translators.
Do you get it? Do you agree? We should update the docs SOP
--
Kévin Raymond
(Shaiton)
11 years, 5 months
