Bug 902500
| Summary: | Publican-based books in GNOME Shell | ||
|---|---|---|---|
| Product: | [Community] Publican | Reporter: | Petr Kovar <pkovar> |
| Component: | publican | Assignee: | Ruediger Landmann <rlandman> |
| Status: | CLOSED DUPLICATE | QA Contact: | tools-bugs <tools-bugs> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | future | CC: | jfearn, me, pkovar, publican-list, rglasz, rlandman+disabled, rlandman, sparks |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-04-18 04:02:19 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Petr Kovar
2013-01-21 19:29:01 UTC
CC'ing publican-list and docs to get community feedback. The .desktop file is needed for other desktop environments, IIRC. I'm pretty sure they are mandatory in the Fedora packaging guidelines. Now that I think about it, I'm not sure why they wouldn't be needed in GNOME. I also seem to remember that we have to tweak the .desktop file that Publican provides when we publish the Fedora Release Notes but I'd let someone else speak to that. Hi, it's highly unlikely this will get addressed by the Publican team. We'd be happy to take patches though. Note that you can use publican to build the HTML etc without using its packaging mechanism, so there is nothing stopping anyone with a minimal understanding of spec files from doing whatever they like with the output. e.g. pop something like this in to a specfile %build publican build --langs all --formats html --publish %install rm -rf $RPM_BUILD_ROOT mkdir -p $RPM_BUILD_ROOT/usr/share/help/ for lang in 'en-US' 'de-DE'; do olang=`sed -e 's/-/_/g'; install publish/$lang/Publican/3.1/html/Users_Guide $RPM_BUILD_ROOT/usr/share/help/$olang/Publican; done Untested, but you get the idea, if you aren't happy with the way it packages things just use publican like any other command line tool and forget it does some automated packaging. I have a spec file that does almost exactly that, and the Release Notes have been using a javascript snippet for a while that redirect the user the the appropriate documents. I'm writing something up on the process of using such a spec file to package our docs now, and can post a link in this ticket for the curious. A few highlights: - Localized files are in subdirectories - Desktop file is localized at build time. The actual action line cannot be localized, ie Exec or URI, but we can localize name and comment. I'm intrigued by the idea of documentation as a search provider. *** This bug has been marked as a duplicate of bug 785751 *** |