[ 
https://issues.apache.org/jira/browse/CAMEL-12422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16426551#comment-16426551
 ] 

ASF GitHub Bot commented on CAMEL-12422:
----------------------------------------

fbolton commented on issue #2280: CAMEL-12422 Fixed language declaration for 
code snippets in documenta…
URL: https://github.com/apache/camel/pull/2280#issuecomment-378842094
 
 
   That's great. Thanks very much, @oscerd !

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Wrong language syntax declarations for code samples in documentation
> --------------------------------------------------------------------
>
>                 Key: CAMEL-12422
>                 URL: https://issues.apache.org/jira/browse/CAMEL-12422
>             Project: Camel
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: 2.21.0
>            Reporter: Fintan Bolton
>            Assignee: Andrea Cosentino
>            Priority: Major
>             Fix For: 2.21.1, 2.22.0
>
>
> AsciiDoc has the ability to support syntax highlighting, which can be enabled 
> by putting the following line before a code sample (e.g. for Java code):
> {code:java}
> [source,java]{code}
> However, there are some places in the documentation where this declaration is 
> used, but the code sample that follows is _not_ Java. This can cause 
> incorrect syntax highlighting or (more seriously) can sometimes cause a 
> documentation build to crash. The following doc files are affected:
> * {{csv-dataformat.adoc}}
> * {{mime-multipart-dataformat.adoc}}
> * {{mongodb-gridfs-component.adoc}}
> * {{snmp-component.adoc}}
> I plan to submit a PR to fix these files.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to