Comments (6)
I noticed a typo:
![ifka sims maia](./res/monos-b-03.png){ width=697px #fig:b03 }
should prob read
![ifka sims maia](.\res/monos-b-03.png){ width=697px #fig:b03 }
then it would be consistent with the line that worked
![af sef ef ](.\res/monos-b-04.png){ width=697px #fig:b04 }
Hope this helps?
from pandoc-fignos.
Does @jrennstich's advice solve the problem, @autotel? I'm a bit unfamiliar with the use of backslashes in that manner.
from pandoc-fignos.
Hi! No, the problem has no relation with the direction of slashes. The problem remains with consistent forward slashes. I think it might have more relation with the code that matches the ref string.
--edit--
I found another place where both cases occur
MD text:
that extend the possibilities of the initial set (figs @fig:b03 & @fig:b04).
![Example of emerging components](./res/monos-b-03.png){ width=697px #fig:b03 }
![Additional example of emerging components](./res/monos-b-04.png){ width=697px #fig:b04 }
--edit 2--
I tried to make it the most likely for the system to find the tags by removing all the other filters from the conversion call (I am converting to ICML)
MD text:
built that extend the possibilities of the initial set (figs {@fig:b03} & {@fig:b04}).
![Example of emerging components](./res/monos-b-03.png){#fig:b03}
![Additional example of emerging components](./res/monos-b-04.png){#fig:b04}
from pandoc-fignos.
I tried using the crossref filter, and it produces the same problems; this means that the problem is on how I wrote the references. I cannot find the problem, though.
from pandoc-fignos.
I finally found the problem: it had to do not with the referencing itself, but with the breaking lines relation among the images. I will explain since this may help others:
In the examples I provided, I removed a line because I thought it would only distract. This is how my text was originally:
MD text:
built that extend the possibilities of the initial set ([@fig:b03; @fig:b04]).
![graph of the iterative process](./res/monos-b-01.png){#fig:b01 width=30%}
![Example of emerging components](./res/monos-b-03.png){#fig:b03 width=30%}
![Additional example of emerging components](./res/monos-b-04.png){#fig:b04 }
I removed the line containing the fig b01, because I thought it was not related to the problem and would make reading easier. I ran into this caveat:
This only works on implicit figures, i.e. an image occurring by itself in a paragraph (which will be rendered as a figure with caption by pandoc)
(from https://hackage.haskell.org/package/pandoc-crossref-0.2.5.0)
My figure is not strictly within the text, but it had a single break instead of a double break, which the working figure does have. Probably the MD parser considered the single break as no break at all. This is sad, because the nice thing about writing in MD is not having to deal with counter-intuitive problems that other formats may have.
In short, the way to solve the not-found figure references is to separate all the target figures with at least to line breaks.
from pandoc-fignos.
Yes, pandoc requires figures to be in their own paragraph. I'm glad that you were able to sort it out.
Cheers,
Tom
from pandoc-fignos.
Related Issues (20)
- Auto-generated caption names want to be bold, when converting from markdown to word.
- Installation of Fignos for windows
- Error producing PDF related to no-prefix-figure-caption HOT 1
- Changing figure caption name with babel in LaTeX
- RuntimeError: Cannot understand pandocversion=3.0.1 HOT 9
- No caption numbers in docx output HOT 4
- "Bad reference" - syntax doesn't work on recent pandoc releases HOT 1
- TypeError in pandocxnos.core.process_refs with Pandoc 2.11 HOT 4
- Pandoc HTML5 Video, Media Fragments HOT 3
- Please clarify documentation for `pandoc-fignos` and `pandoc-eqnos` when a pandoc defaults file is used
- ! LaTeX Error: Environment fignos:no-prefix-figure-caption undefined. HOT 3
- Feature Request: new caption separator for respecting some language typo rules
- Label and sizing HOT 3
- Error when filtering with 'python -m pandoc_fignos json'
- Hardwire figure numbers in LaTeX
- Using a figure caption as referenced label
- Feature Request: `--fail-if-warnings`
- Issues when converting "*.tex" to "*.html"
- \theHfigure undefined
- Figure reference links on epub files are wrong HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pandoc-fignos.