-
Notifications
You must be signed in to change notification settings - Fork 386
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
Check footnote's consecutive paragraphs #1198
Comments
Footnote consecutive paragraph now starts with ...., since ~~~~ would already have a strike-thru meaning in some markdown visualizers. |
Nevermind, 4 dots are ambiguous since it's unknown if the author omitted some text. |
pdf render updated: swfsql/genpdf@bc01ca4 there are new options, such as "check footer". It will count multi-lined footers from original files and will compare with the selected translations. ps. the original file footer was incorrect, it appears that crowdin erased that explicit formatting information, although it was in the end of the file. So the count differences are shown: |
Before closing, it needs to also verify if the total number of footnotes, not only their line count, is the same. |
Moved to swfsql/genpdf#26 |
In markdown, if a footnote has a consecutive paragraph, it starts the line with " " (four spaces). This is a formatting information that is easy to lose when translating.
So, for future texts, "~~~~" should be used instead, so that this information is much less-likely to get lost. Then I'll just replace it back to spaces before rendering the files.
Also, it is very desired to have a script to check, on original files, if there is any case of those consecutives paragraphs (any case of " " on the beginning of the line). If this is the case, the footnote and this cases count should be recorded, and then later, compared to the translated text. If the translation's count is less, it should be notified that there is formatting information that was lost.
Then I'll just go and fix it on Github.
The text was updated successfully, but these errors were encountered: