>I acknowledge the history of the digikam help handbooks, but I'm 
>uncomfortable with that approach for Trinity.
>
>Let's split the English component only and merge that directly 
>into 
>the existing Digikam sources. That is how all other apps are 
>designed. I have already tested that.
>
>The remaining languages can move to a new module, 
>applications/digikam-doc-i18n.
>
>Most users who do not speak i18n languages don't want to install 
>all of those components just to obtain access to the 
>digikam/showfoto handbooks. Further, as is common with all other 
>Trinity apps, there should be a default handbook installed with 
>the package. :)

I have this all tested.

I have a single patch to push for the existing Digikam, which will 
build the English handbooks for Digikam and Showfoto.

I have the proposed digikam-doc-i18n contents tested so only the 
i18n handbooks are built and installed. My digikam-doc-i18n files 
also include copies of the master admin and cmake files.

All I need now is for somebody to create a new module in the main 
repository named digikam-doc-i18n. With the new upstream module I 
can push the whole directory and we'll be done. I would create the 
new module myself but I don't know whether I have permissions to do 
that and I also don't know all that is involved.

Digikam and Showfoto handbooks standing by!

Darrell