We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow a task to handle a sourceset for various languages.
Consider that we have a standard setup like
asciidoctor { sourceDir 'src/docs/asciidoc' sources { include 'index.adoc' } resources { include 'images/**' } outputDir "${buildDir}/asciidoc" }
This infers a normal layout of
src/docs/asciidoc/index.adoc /images/*.*
The outputs will end up in build/asciidoc (assuming a conventionalbuildDir).
build/asciidoc
buildDir
If we now add a DSL keyword such that
asciidoctor { languages 'en', 'es' }
it will imply that we have an English and a Spanish sourceset and that the file layout will now be
src/docs/asciidoc/en/index.adoc /en/images/** /es/index.adoc /es/images/**
Outputs will now end up in
build/asciidoc/en /es
We shall need to accommodate the use case where resources could be language specific
asciidoctor { resources 'en', { } resources 'es', { } }
and this will only copy that specific resources when the specific language is being processed.
If the languages keyword is not used, the bhevaiour will be exactly as it is today.
languages
For the case of combining backends and languages
asciidoctor { outputOptions { backends 'html', 'docbook' } languages 'en', 'es' }
the outputs will be
build/asciidoc/en/html /docbook /es/html /docbook
The text was updated successfully, but these errors were encountered:
WIP: Generate documents from multiple language sources (asciidoctor#392)
15bd8da
c8018dc
Merge pull request #398 from ysb33r/multi-language
7024a6f
Generate documents from multiple language sources (#392)
Totally agree. Looks good. Languages as a facet is the right way to go.
Sorry, something went wrong.
c59c96b
No branches or pull requests
Allow a task to handle a sourceset for various languages.
Where we are today
Consider that we have a standard setup like
This infers a normal layout of
The outputs will end up in
build/asciidoc
(assuming a conventionalbuildDir
).What we want to add
If we now add a DSL keyword such that
it will imply that we have an English and a Spanish sourceset and that the file layout will now be
Outputs will now end up in
We shall need to accommodate the use case where resources could be language specific
and this will only copy that specific resources when the specific language is being processed.
Keeping current behaviour
If the
languages
keyword is not used, the bhevaiour will be exactly as it is today.Dealing with multiple backends
For the case of combining backends and languages
the outputs will be
Other things to deal with
The text was updated successfully, but these errors were encountered: