-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Are necessary any implicit changes made by GitLocalize? #204
Comments
@sotayamashita these changes seem out of scope for a translation engine. Are they necessary? |
@RichardLitt GitLocalize changes some markdown following flow. In GitLocalize, we parse markdown and convert it into HTML to translate. After translating, we convert HTML to markdown based on commonmark spec. A series of the flow, we change some markdown. We understand that issue but it will rendered same before. Is there a problem? Thanks in advance. 🙇 |
Good to know. You're right, most of these are superficial. However, the TOC changes aren't - as far as I know, they will break the links. @buslov can you confirm this? |
@RichardLitt, you are right. I suppose that GitLocalize just copies links from English source. We could add some tests (#205) to Travis CI to prevent any merges with broken links. |
GitLocalize adds some changes when making a pull-request:
The text was updated successfully, but these errors were encountered: