As i've learned with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=651650
No matter if a guide is 100% translated, it won't be published automatically, *someone* should publish the work done.
I'd like to join the publishers group in order to let people access to last up-to-date translations we are working on (including peer reviews).
I'm reading this howto, but i wonder if with the new Publican version (2.3), we are actually forced to logout an then login with en_US locale to avoid buggy links in the published guide:
http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
Any other guide i should read to understand better the publishing process?
Thanks in advance,
Jesús Franco http://identi.ca/tzk http://fedoraproject.org/wiki/User:Tezcatl
On 11/11/2010 08:51 AM, Jesús Franco wrote:
As i've learned with this bug: https://bugzilla.redhat.com/show_bug.cgi?id=651650
No matter if a guide is 100% translated, it won't be published automatically, *someone* should publish the work done.
I'd like to join the publishers group in order to let people access to last up-to-date translations we are working on (including peer reviews).
Done -- welcome aboard and thanks for the offer of help.
I'm reading this howto, but i wonder if with the new Publican version (2.3), we are actually forced to logout an then login with en_US locale to avoid buggy links in the published guide:
http://fedoraproject.org/wiki/Publishing_a_document_with_Publican
[cc'ing this to trans list, as others there might like to know more about this problem]
As mentioned on the wiki page, you must only publish documentation when logged in with en_US as your locale. However, this has nothing to do with buggy links -- I think you're referring to a different bug with a different cause and different symptoms.[0]
The problem in this case is that publishing from a system when logged in with a locale other than en-US seems to break the navigation menus. Specifically, the labels that say "collapse all", "search", "Map" etc., plus any text with non-Latin characters elsewhere on the page[1] -- and it breaks the menus /in all languages/, not just the language in which you are publishing.
Unfortunately, the problem is poorly understood at the moment, because those of us on the Publican team haven't had time to investigate this properly. We don't even know yet which specific set of circumstances creates this problem. Now that Red Hat Enterprise Linux 6 is launched, we should have some more time :)
If you want to verify the problem on your own system, you could try:
* stay logged in with your Spanish locale * check out web.git, as described on the "Publishing" wiki page * create a new, local git branch and change into it: "git branch temp" and "git checkout temp", for example * build and install a book, as described on the "Publishing" wiki page * browse to the public_html/index.html page, and look at the navigation menus in a few languages to see if they look broken.
Any other guide i should read to understand better the publishing process?
The Publican User's Guide[2] explains the mechanism from Publican's side, in particular, Chapter 6. Building a website with Publican.[3] And of course, please feel free to ask questions on the docs list, and also on the Publican list[4].
Cheers Rudi
[0] https://bugzilla.redhat.com/show_bug.cgi?id=648126
[1] http://rlandmann.fedorapeople.org/Screenshot-User%20Guide%20-%20Mozilla%20Fi...
[2] http://jfearn.fedorapeople.org/en-US/Publican/2.3/html/Users_Guide/index.htm...
[3] http://jfearn.fedorapeople.org/en-US/Publican/2.3/html/Users_Guide/sect-User...
Has been a long time since the original thread, but i think deserved the proper reply.
El Thu, 11 Nov 2010 10:05:34 +1000, Ruediger Landmann escribió:
As mentioned on the wiki page, you must only publish documentation when logged in with en_US as your locale. However, this has nothing to do with buggy links -- I think you're referring to a different bug with a different cause and different symptoms.[0]
I must say my abilities to track properly the cause of the bugs are very poor. This said, i've simply renamed the buggy filenames causing the software management guide published in Castilian was unreadable in the html navigable version, with git mv {buggyname} {name-expected-by-link}.
If you want to verify the problem on your own system, you could try:
I've actually tried with the publican version 2.5, so, i think this could be a task for updating the wiki (i'm requesting for comments).
- stay logged in with your Spanish locale * check out web.git, as
described on the "Publishing" wiki page * create a new, local git branch and change into it: "git branch temp" and "git checkout temp", for example
- build and install a book, as described on the "Publishing" wiki page *
browse to the public_html/index.html page, and look at the navigation menus in a few languages to see if they look broken.
Everything seemed ok to me in the languages i can recognize some words at least.
The Publican User's Guide[2] explains the mechanism from Publican's side, in particular, Chapter 6. Building a website with Publican.[3] And of course, please feel free to ask questions on the docs list, and also on the Publican list[4].
I'm sorry for commiting this task so late. But i've finally managed this and i wanted to say thanks for the time you've taken to teach me how to do the right things every time i asked for your help.
Cheers Rudi
Inspiration for commiting some tasks has come to me. I'll check bugs to see if there is anything i can help.
Now i'm really in! :)
2010/11/10 Jesús Franco tezcatl@fedoraproject.org:
I'm reading this howto, but i wonder if with the new Publican version (2.3), we are actually forced to logout an then login with en_US locale to avoid buggy links in the published guide:
Typing LANG=C command in the terminal before running Publican in it seems sufficient to not break menus.
Regards,
-
Jesús Franco -
Piotr Drąg -
Ruediger Landmann