[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: CSS style for the documentation pages?


On Sun, Apr 27, 2014 at 05:17:14PM +0200, Stéphane Blondon wrote:
> For info, I subscribed to the debian-www mailing list yesterday, so
> there is no need to remember to keep me in the thread.
> 2014-04-26 7:37 GMT+02:00 Osamu Aoki <osamu_aoki_home@nifty.com>:
> > "installation-guide" is rather a big package.  Initially, other packages may be
> > easier to work on.[...]
> > I think maint-guide is a good starting point since it is rather a simple
> > package.
> Thanks for your explanations! :-)
> I installed all the packages in "maint-guide" control files.

Are you using stable or unstable package?

> (Strangely ?), german target works only after installing
> texlive-lang-german which is commented in control file. 

I have it in the released package 1.2.32

> zh-cn and zh-tw targets don't compile. 

NOPDF   :=      zh-cn zh-tw

> I guess the computer lacks some packages
> but I focused about changing style than fixing the languages.

There are more languages in makefile but for packaging, less are build
as defined in debian/rules I do not think I build zh-cn zh-tw for

> I get a draft of what it is planned to looks like.
> It's temporary downloadable at
> http://stephane.yaal.fr/tmp/maint-guide-1.2.31.tar.xz

In general, it looks very pretty on large screen with width as big as
8.5 inch.  But since quite a bit of side margins are used, it waste side
spaces and folds line too much on smaller screen.  Anyway, HTML
formatting for easthetics is not something I am good at.  I think you do
a fine job.

FYI: The latest version is 1.2.32 or even at git:
 See http://anonscm.debian.org/gitweb/?p=ddp/maint-guide.git
or get the latest by
 $ git clone https://alioth.debian.org/anonscm/git/ddp/maint-guide.git

Please note some recent commited changes are not tested by me.

> I can extract it and load files like index.en.html or index.ca.html in
> your browser.
> Please just consider it only like several ugly hacks[1] based on
> copy-pastes in order to get a quick demo.

Yes, that is a good start.

> >> > Quoting Simon Paillard <spaillard@debian.org>:
> >> > >The other way I've tried some months ago was using publican for release
> >> > >notes,
> >> > >for which buxy provided a nice Debian css (publican-debian).
> Is publican-debian currently used in a project (whatever it is)?
> It could be useful to read the configuration files and the way it
> works for this project.
> > (If anyone wish to test build XML from maint-guide, run "make xml" first
> > to get all translated XML files first.)
> I probably missed something obvious but "make xml" didn't work because
> there is not "xml" target in the Makefile.
> However I can generate translated ca, fr, ... files.

Are you looking at isource package of the 1.2.32 version?  I see:

.PHONY: xml
xml: $(SRC_XML)
> By the way, German is written twice in LANGS_PO in Makefile. It does
> not really matters, but one 'de' is removable:
> -LANGS_PO    := ca de es fr it ja ru de zh-cn zh-tw
> +LANGS_PO    := ca de es fr it ja ru zh-cn zh-tw

That's buggy old subversion file.

> > Once we are successful doing this non-publican path, updating others are
> > rather trivial using the same path.  It cause minimal change and no
> > large dependency.  If no one comes up with solid path, I will eventually
> > do this when I feel like it.  But not now.
> We could have an easy first step by just updating the current files:
>  - maint-guide.css update by merging style from current
> maint-guide.css, publican and the main website css.
>  - the pictures (up, back, warning, etc.) by copying the publican ones
> in /usr/share/xml/docbook/stylesheet/nwalsh/images. It requires to
> change the format (png to gif) or to change the generated files.


> In a second step, the documentation would be improved by using
> publican directly or using publican-debian inside the current
> Makefile.

That's true.  

> What do you think about this two-step strategy?

There are for HTML.  What do you think about PDF woth FOP issue.

Step 1:
 Update HTML build to make it look nicer
Step 2:
 Check usability of publican with FOP.
Step 3:
 Format PDF (with new publican or old LaTex)


Reply to: