Replies: 4 comments 15 replies
-
|
Try using a |
Beta Was this translation helpful? Give feedback.
-
|
It seems you need to generate a docx with the "Source Code" text to find it.
|
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry, but I'm not sure I understand your suggestion. Could you please provide detailed steps on how to prepare a reference document with "Source Code" style that has no indentation? Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
Save the following code block in Test source code style in docx:
```html
<!DOCTYPE html>
<html lang="en-US">
<head>
</head>
<body>
</body>
</html>
```Then run the command to render pandoc -o output.md input.docxOpen the generated |
Beta Was this translation helpful? Give feedback.
-
|
When I open the generated Here is how I did the conversion:
|
Beta Was this translation helpful? Give feedback.
-
|
I'm not seeing any indentation if I do, for example, I notice that in your traget.md all the source is indented. That may be the problem. |
Beta Was this translation helpful? Give feedback.
-
That's the problem and the whole point of this discussion :) |
Beta Was this translation helpful? Give feedback.
-
|
Oh right, you're converting from docx to markdown. Apologies, I misunderstood some of your original comment -- I had thought that the backticks were part of pandoc's output. But here's what I'm seeing: That output is completely fine! It's a different style of code block -- actually the original Markdown style. The indentation indicates that it's a code block. Don't worry, the content will not be indented if you convert this to another format. |
Beta Was this translation helpful? Give feedback.
-
|
To be more explicit, there are two kinds of code blocks in pandoc's Markdown: indented code blocks (original Markdown style) and fenced code blocks. The markdown writer uses indented code blocks when no language is specified. (And this information isn't available in a docx source.) |
Beta Was this translation helpful? Give feedback.
-
|
Semantically, is equivalent to |
Beta Was this translation helpful? Give feedback.
-
|
That's not my scenario. I want the backticks in the target.md markdown file (along with the programming language hint) as they appear in the source.docx file, just without the additional indentation. I'm not arguing against the semantic equivalence you described; it's just not my case. |
Beta Was this translation helpful? Give feedback.
-
|
OK, I thought input.docx was your input, but it's actually source.docx. |
Beta Was this translation helpful? Give feedback.
-
I don't expect the markdown code block syntax to work in docx, just as I don't expect the "Source Code" style to "work" in docx. If I don't include the backticks in the "Source Code" styled text, then I would need to add them in the target file (including the programming language hint) post-conversion, which would become a nightmare. If that's too much to ask, how can I instruct Pandoc to output a specific Word paragraph "as-is" without any pre-processing during conversion? The reason I used the "Source Code" style initially is that, by default, < and > are correctly escaped in the output file, but this also results in HTML source code being escaped. |
Beta Was this translation helpful? Give feedback.
-
|
Alternatively, if you are not comfortable with processing format-specific directives within the docx, then the "code-block" contract can be enhanced to include the programming language in the style name. For example, text styled with a style named "HTML Source Code" or "HTML Code Block" would instruct Pandoc to wrap the text with code markers and include the programming language hint in the output file when converting docx to markdown, perhaps using the first component in the style name for the language string. |
Beta Was this translation helpful? Give feedback.
-
|
In any case, as mentioned, I would very much appreciate a way to instruct Pandoc not to encode or preprocess specific paragraphs during conversion and write the text "as-is" to the output file, effectively providing an escape hatch for those cases where "inline assembly" is required. This can be as simple as skipping encoding of text styled with a named style such as "Pandoc No Encoding" or similar wording. |
Beta Was this translation helpful? Give feedback.
-
Don't expect this. That's expecting pandoc to be treating docx content as if it is markdown. Backticks in a docx Source Code section are just backticks.
You could work around this by using a Lua filter and a simple convention. E.g. have each code block in the docx source start with a line containing
There's no way to do this. (And I'm sure you don't mean this literally ; you don't want a big block of OpenXML in your markdown, but that's what is in the docx container.) |
Beta Was this translation helpful? Give feedback.
-
Does the indentation occur before or after the Lua script executes? I don’t want to prepare the script only to end up back at square one. |
Beta Was this translation helpful? Give feedback.
-
|
The writer will produce an indented code block if there is no class indicating the language. If the filter adds such a class, then the writer will produce a fenced code block. |
Beta Was this translation helpful? Give feedback.
-
I have a Word document containing some HTML, which I wrapped with
htmlcode block markers.Example:
```html
```
I created a style in Word called “Source Code” and applied this style to the entire wrapped HTML. I then converted the docx to markdown using the following command:
The entire code block is shifted by 4 spaces in the output file. I do not want this shift.
Any assistance with resolving this issue would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions