-
Notifications
You must be signed in to change notification settings - Fork 29
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generated files are in ANSI format, not UTF-8 #77
Comments
Could you upload the original file as well as the generated one? |
Sure, I will have a look at it again. I have had a lot of use of your project to get started but now I have created my own system (MS Word templates, unfortunately). But if you need it for debugging purposes I will get back soon with the files |
@hmogensen no that's okay, I don't want to take up too much of your time. I'd love to learn why you switched to Word templates and any suggestions you have for RDM. Feel free to post here, or email me at jdgiese@innolitics.com |
The original file in rdm\init_files\documents\ is set to UTF-8. Then I run pandoc from Git bash, and the following file is generated:
If I open the 510.md file in Notepad and save as utf-8 it works. |
Short answer to your question: the place where I work have their predefined word templates, so I couldn't just use the markdown files. Also, as you mentioned in the README or FAQ, most 'normal' people prefer working in Word as opposed to using text-based files. I took inspiration from your structure and created generic Word documents (in Swedish) corresponding to each required attachment. I am working with the EU's medical device regulation (MDR), also for non-software product so it does not translate perfectly. |
I do not know if this is a feature, bug or neither, but when I run the make command the generated files are generated as ANSI format. This causes an error when trying to convert the generated document (e.g. release/510.md) to a word document using pandoc
Running MS Windows 10 Enterprise, Python 3.8
The text was updated successfully, but these errors were encountered: