And what if we incorporate documentation for all languages ​​into an existing git repository digikam and generate documentation could be done as build options? For example --with-doc and --with-doc-i18n or --without- doc and --without-doc-i18n.

That could be palatable.

On reflection, I notice there are some apps that automatically include i18n docs when building the package. For example, amarok and kipi-plugins. Pushing the digikam docs into the existing digikam sources would be no different.

If we add configuration options, the default should be --with- doc=true and --with-doc-i18n=false. Using --with-doc=true as a default ensures at least the English handbook is built with the standard package, just like most Trinity apps. Yet explicitly adding the --with-doc option allows for not building the docs. For example when people prefer building minimal footprint packages.

If we add those configuration options then we should do likewise for all affected apps like amarok and kipi-plugins.

So how about this:

I push the digikam docs into the existing digikam sources. Right now that means all i18n docs are compiled when compiling digikam. No different than amarok and kipi-plugins.

I open a bug report to add --with-doc and --with-doc-i18n configuration options to all Trinity apps, and equivalent cmake options.

Darrell