asciidoctor-go/inline_parser.go, branch dev

all: fix parsing inline format with escaped character

2026-02-18T04:12:44Z

If the text inside the inline format contains escaped character, the parsing failed to find the closed character which cause the format is not rendered as expected.

all: remove the "nolint" tag

2025-02-18T14:09:43Z

The nolint tag is to ignore being linted by golangci-lint. Since we are not using golangci-lint anymore, we can remove it.

all: group all image related method and functions into single file

2024-10-15T05:37:13Z

This is to make it easy to see how it parsed and how it written to HTML, make the code more searchable. While at it, add test for block image.

all: comply with linter recommendations

2024-03-05T11:00:34Z

all: replace module "share" with "pakakeh.go"

2024-03-05T11:00:34Z

all: replace linter golangci-lint with revive and shadow

2023-12-09T16:36:50Z

The golangci-lint does not output any results anymore Either we are getting good at writing Go or the linter itself is become less good. We also have seen that the latest golangci-lint is failed to build with Go tip, a simple "make" on the golangci-lint never success in my experiences. This changes fix all the output reported by the revive and shadow.

all: ignore parsing block image in paragraph

2023-03-02T16:00:19Z

Previously, if we have block image in paragraph, we parse it as inline image but with invalid src, for example image::my.png[multi line] would be parsed as . This is incorrect according to asciidoctor output.

all: implement inline macro for passthrough ("pass:")

2022-11-27T14:14:18Z

The inline passthrough "pass:" can be used to control the substitutions applied to a run of text. Ref: https://docs.asciidoctor.org/asciidoc/latest/pass/pass-macro/

all: make the macro parser independent, out of inlineParser

2022-11-23T14:48:29Z

The idea is to move the parser to macro later so it can be reused by html substitution.

all: implement macro "footnote:"

2022-10-20T15:09:31Z

Macro footnote grammar, ---- "footnote:" [ REF_ID ] "[" STRING "]" ---- In asciidoctor, footnote can be placed anywhere, even after WORD without space in between. The REF_ID, define the unique ID for footnote and can be used to reference the previous footnote. The first footnote with REF_ID, should have the STRING defined. The next footnote with the same REF_ID, should not have the STRING defined; if its defined, the STRING is ignored.