Re: Manpage writing guidelines? - Mailing list pgadmin-hackers

From Raphaël Enrici
Subject Re: Manpage writing guidelines?
Date
Msg-id 436F0CB6.7040408@club-internet.fr
Whole thread Raw
In response to Re: Manpage writing guidelines?  (Dave Page <dpage@vale-housing.co.uk>)
List pgadmin-hackers
Dave Page wrote:
>
<snip>
> 5) Load the project into Microsoft HTML Help Workshop. Check the index
> structure, and move at least 1 item. If necessary, move it, then move it
> back. This makes the IDE rewrite the index file and fixup an broken markup,
> or markup it doesn't like for reasons you probably won't ever be able to
> spot!

I remember some discuss on the list where it was considered to be able
to do this without MS Workshop. Some track to follow concerning this?

<snip>
>
>>I think I should include the PostgreSQL french manual in pgAdmin but I don't
>>know if there is an automated way to do the conversion docbook sgml to chm.
>>Can you explain how you did it ?
>
>
> The idea always was to get full manuals for each language, but then
> originally we didn't bundle the pgAdmin and Slony docs. The problem now is
> that if we do so, the tarball is rapidly going to get huge. I think if we're
> going to do this, we a) need some serious commitment form the translators
> that it will be maintained, and b) need to look at packaging translations as
> 'language packs' that can be downloaded separately from the main package in
> both the source and binary distributions.
>
> Thoughts?

If we decide to provide separated language pack we should definetly take
in consideration the impact on packaging stuff and/or the ability to
install these packs in user mode and if so the support of indicents due
to such user install. However, I think that may be a good idea if well
thought and done.

Regards,
Raph

pgadmin-hackers by date:

Previous
From: "Hiroshi Saito"
Date:
Subject: The problem in Japanese.
Next
From: "Dave Page"
Date:
Subject: Re: SVN Commit by dpage: r4685 - trunk/pgadmin3