Hi,
Is the rendering done by asciidoctor command and asciidoctor maven plugin done exactly in the same way ? Why this question : because I didn't get the same result using this instruction : asciidoctor -b html5 -T A/target/maven-shared-archive-resources/asciidoctor-backend/haml/html5 -a embedAssets -a stylesheet=target/content/LMSClass/A/css/my_theme.css A/docs/new_proj_pg1.txt --out-file target/content/LMSClass/A/new_proj_pg1.html and what maven plugin do [DEBUG] Goal: org.asciidoctor:asciidoctor-maven-plugin:0.1.3.1:process-asciidoc (output-html) [DEBUG] Style: Regular [DEBUG] Configuration: <?xml version="1.0" encoding="UTF-8"?> <configuration> <attributes> <max-width>1024px</max-width> <icons/> <stylesheet>/Users/chmoulli/Temp/openshift/modules/A/target/maven-shared-archive-resources/css/my_theme.css</stylesheet> </attributes> <backend default-value="docbook">html5</backend> <embedAssets>true</embedAssets> <eruby>${asciidoctor.eruby}</eruby> <outputDirectory default-value="${project.build.directory}/generated-docs">/Users/chmoulli/Temp/openshift/modules/A/target/generated-docs/LMSClass/A</outputDirectory> <sourceDirectory default-value="${basedir}/src/main/asciidoc">/Users/chmoulli/Temp/openshift/modules/A/docs</sourceDirectory> <templateDir>/Users/chmoulli/Temp/openshift/modules/A/target/maven-shared-archive-resources/asciidoctor-backend/haml/html5</templateDir> </configuration> With asciidoctor executed with command line the rendering of the admonition icons (font-awesome) is done correctly as I can see the icons and not with asciidoctor maven plugin / command line Remark : - HTML + CSS generated is the same, - There in both cases a link to css - I become crazy as HTML generated is the same :-( </style> <link rel="stylesheet" href="http://cdnjs.cloudflare.com/ajax/libs/font-awesome/3.2.1/css/font-awesome.min.css"> <style> Question : How can I very that font-awesone / icons works correctly ?
Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist Twitter : @cmoulliard |
Are you using Asciidoctor ruby version 0.1.3 when doing the comparison? If not you could do that, or build and use the snapshot of HEAD to use asciidoctor 0.1.4.
—
Sent from Mailbox for iPhone On Tue, Nov 26, 2013 at 8:30 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:
|
I use asciidoctor 0.1.4 on my mac :
asciidoctor --version Asciidoctor 0.1.4 [http://asciidoctor.org] and this version for asciidoctor maven plugin : 0.1.3.1
I have done a test using asciidoctor maven plugin 0.1.4-SNAPSHOT and get the same issue Remark : That should be great to generate the asciidoctor command used by maven plugin so we can, in case of trouble, copy/paste the command and
compare with command life if there are differencesOn Tue, Nov 26, 2013 at 5:14 PM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist Twitter : @cmoulliard |
The idea of generating the command is a good idea. Please add an issue to AsciidoctorJ for that.
—
Sent from Mailbox for iPhone On Tue, Nov 26, 2013 at 10:43 AM, ch007m [via Asciidoctor :: Discussion] <[hidden email]> wrote:
|
Done : https://github.com/asciidoctor/asciidoctor-maven-plugin/issues/85
Any idea about the issue that I have ?
Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist Twitter : @cmoulliard |
Administrator
|
In reply to this post by LightGuardjp
Indeed, that would make good log output. I suspect your rendering issue is, like Jason said, due to the fact that the Maven plugin is using 0.1.3. AsciidoctorJ could also log the Asciidoctor gem version, or all the gem versions for that matter. -Dan On Nov 26, 2013 10:47 AM, "LightGuardjp [via Asciidoctor :: Discussion]" <[hidden email]> wrote:
|
Dan, can you move the issue to AsciidoctorJ? I think that's an admin feature and I know I'm not an admin on asciidoctorj.
—
Sent from Mailbox for iPhone On Tue, Nov 26, 2013 at 10:54 AM, mojavelinux [via Asciidoctor :: Discussion] <[hidden email]> wrote:
|
Administrator
|
Done. I had to refile it. -DanOn Tue, Nov 26, 2013 at 10:57 AM, LightGuardjp [via Asciidoctor :: Discussion] <[hidden email]> wrote:
-- Dan Allen | http://google.com/profiles/dan.j.allen |
Been able to figure out the issue. I was not using the same attribute in both cases but :icons: font (the one working) and :icons: (which was not working) for admonitions Remarks : - 'font' attribute should be renamed to font-awesome (or icons:: [font-type or font-family="font-awesome"] to avoid ambiguity as by default this is not evident to understand that (:icons: font) means that we will render a image link using the <i> tag and that font-awesome css is used to display the image
- As there are other css font icons available (google icons, icoMoon, font-awesome, typicons, http://sixrevisions.com/resources/free-icon-fonts/), we should certainly use a better name to identify the font css to be used.
- Imagine that in a page we would like to mix 2 or more css fonts (font-awesome, icomoon, ...) for the icons to be displayed, that means that we should have the possibility when creating the admonition (block_admonition_html.xxx) or image (inline_image_html.xxx) to specify which icon-class/type we would like to use. Example : ìmage::src[`alt`, `width`, `height`,`font-family or font-type`] where font-type or font-family (not yet sure about the name) corresponds to font-awesome (supported now) or others that we could supported in the future (icoMoon, GoogleFont, http://sixrevisions.com/resources/free-icon-fonts/ )
On Wed, Nov 27, 2013 at 3:00 AM, mojavelinux [via Asciidoctor :: Discussion] <[hidden email]> wrote:
Charles Moulliard Apache Committer / Architect @RedHat Twitter : @cmoulliard | Blog : http://cmoulliard.github.io
Charles Moulliard
Apache Committer / Technologist Evangelist / Blogger / MiddleWare Specialist Twitter : @cmoulliard |
Free forum by Nabble | Edit this page |