If an attachment path is:
/foo/<BUNDLE_NAME>/bar/baz.png
That attachment is copied to:
<HUGO_BASE_DIR>/content/<SECTION>/<BUNDLE_NAME>/bar/baz.png
i.e. the attachment path *after* "/<BUNDLE_NAME>/" is retained.
Use plist-put and plist-get instead of passing the description value
via a global variable.
To my surprise, the plist-put and plist-get works across functions!
This works **only for links TO per-file export flow Org files**.
- The linked files must not have a custom `#+export_file_name` set.
- The linked files should not be page bundles.
This commit implemented very basic cross-linking support as per the
spec in https://github.com/kaushalmodi/ox-hugo/issues/131. So the page
bundle names, section names, export file names, etc set within the Org
file are not resolved.
Add new attribute #+ATTR_SHORTCODE: to specify positional arguments
for the shortcode following ":args".
Example:
#+attr_shortcode: warning
#+begin_alert
This is a warning!
#+end_alert
Above exports as (given HUGO_PAIRED_SHORTCODES is set as "%alert"):
{{% alert warning %}}
This is a warning!
{{% /alert %}}
https://github.com/kaushalmodi/ox-hugo/issues/119
---
This commit is a refinement over
74cb3c2ec8:
- It gets rid of the requirement to use ":args" for positional
arguments.
- Removes unnecessary duplicate syntax (use of :class with
attr_html). If someone wants to have the Org document compatible
with more exporters they should simply *not* use
HUGO_PAIRED_SHORTCODE, and instead rely on the default Special
Blocks behavior (wrapping the text with div or HTML5 tags).
Add new attribute #+ATTR_SHORTCODE: to specify positional arguments
for the shortcode following ":args".
Example:
#+attr_shortcode: :args warning
#+begin_alert
This is a warning!
#+end_alert
Above exports as (given HUGO_PAIRED_SHORTCODES is set as "%alert"):
{{% alert warning %}}
This is a warning!
{{% /alert %}}
For re-usability of Org document with ox-html, below will also result
in the exact same ox-hugo export:
#+attr_html: :class warning
#+begin_alert
This is a warning!
#+end_alert
Simply: #+attr_shortcode -> #+attr_html
:args -> :class
https://github.com/kaushalmodi/ox-hugo/issues/119
Also, now the target and rel attr are once again passed on to the
figure shortcode (a better solution to straightaway discarding those
as done in
e92fcf0037).
Those attributes will still be ineffective as the internal figure
shortcode does not recognize those. But this can be fixed if Hugo adds
the support for those, or if a user simply overrides the internal
shortcode with their custom figure shortcode with that support added.
- [X] Inlined non-hyperlinked images, no meta or only alt -- Use Markdown image syntax
- [X] Inlined hyperlinked images, no meta or only alt -- Use Markdown image syntax
- [X] Inlined non-hyperlinked images, meta other than alt -- Use HTML img
- [X] Inlined hyperlinked images, meta other than alt -- Use HTML img
https://github.com/kaushalmodi/ox-hugo/issues/125
It's conventional to write a shortcode with a space after the starting
"{{<" (or "{{%") characters and a space before the ending pairs.
So do:
{{< SHORTCODE >}}
Not:
{{<SHORTCODE>}}
This commit makes that space insertion consistent for the exported
figure and highlight shortcodes.
The Markdown form [{{< figure .. >}}](some link) results in wrapping
the <figure> in <a> in the final HTML, which is invalid.
- [X] Non-inlined hyperlinked images -- Use link in figure
https://github.com/kaushalmodi/ox-hugo/issues/125
One minor behavior change: Now <a> tag attributes like "target" and
"rel" cannot be applied *only to* the links that images hyperlink
to. The reason is to make the exported Markdown generate valid HTML,
and with how the "figure" shortcode is designed in HTML, those
parameters are not passed onto the <a> element in the generated
<figure> element.
Kaushal Modi