ammachado opened a new pull request, #26382:
URL: https://github.com/apache/camel/pull/26382

   ## Summary
   
   Backport of #26380 to `camel-4.18.x` for apache/camel-website#1746: the 
`components/4.18.x` pages below have no `.md` mirror because they render 
mis-nested HTML, which the website's HTML-to-Markdown step skips.
   
   A `*` inside a single-backtick span is still parsed as a formatting mark, so 
spans such as `` `mail.smtp.*` `` pair with a later `*` and produce 
`<code>…<strong></code>…</strong>`. These spans now use literal monospace (`` 
`+…+` ``). Formatting only; no wording changes.
   
   Pages (the website publishes only `docs/components` and the core engine docs 
from this branch):
   
   - `mail-component`
   - `others/leveldb`
   
   This branch has no catalog copy of these docs, so only the two sources 
change.
   
   ## Not a straight cherry-pick
   
   #26380 also touches user-manual pages that this branch does not publish, and 
the mail doc sits at different line numbers here, so the change is ported by 
hand. **The leveldb change is new**: the component was removed from `main`, so 
it is not part of #26380 and has not been reviewed there.
   
   ## Verification
   
   Rendered with Asciidoctor.js 3.0.2 (the camel-website build version) and 
checked with `node-html-parser`'s `valid()`, the condition under which the 
Markdown generator loses the article:
   
   - Before: both sources are invalid.
   - After: both are valid, and no `<code>` element contains `<strong>`, `<em>` 
or `<mark>`.
   - Scanning every `.adoc` under `docs/` and `*/src/main/docs/` on this 
branch, these two were the only published sources that rendered invalid.
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code) on behalf of 
Adriano Machado (@ammachado)
   
   _This was generated by an AI agent and may contain inaccuracies. Please 
verify before relying on it._
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to