2nd level markdown bullet indentation incorrect in translations

Crowdin Issues
1

I’m round tripping some markdown that that has multi level bullets. The translations are stripping off some of the indentation so that the bullets are not recognized as bullets. You can see the effect here where left side is the translation:

image
image1533×1283 163 KB

  1. This happens on all three translations of the doc
  2. It did not fix this when I:
    • modified the original doc (in another part of the doc) and round tripped
    • renamed the doc in crowdin, reimported the doc and deleted the original (i.e. to recreate doc with original translations, pulled updates.

Original English version

Is there some setting I am getting wrong?

2

Hi there,

The behavior you’re seeing with indentation in code blocks is expected due to how Markdown formatting works. Markdown does not always retain indentation precisely, especially within lists and nested structures. This is inherent to the format itself and not something controlled by our system. The file you received on the export should be 100% valid and ready to use.

However, it may be possible to adjust the formatting using a Custom Post-Export Processor in Crowdin. This could help ensure the required indentation is preserved upon export.

Hope this helps :slight_smile:

3

@Dima Respectfully, if I pass markdown through crowdin without any translation added, and the output indentation is different, this is a flaw in crowdin.

The indentation is not just different for code blocks, but in the bullets themselves. Markdown requires consistent indentation, so by stripping the space vitepress infers the new bullet just has an accidental preceding space.

I can of course try this post export processor (than you for this advice) but this is definitely a crowdin bug.

4

@hamishwillee ,

I understand that consistent indentation is crucial for Markdown, and the issues you’re experiencing are not ideal.

Please note that we rebuild the file according to our parsers on the export, so technically, the file you received may not be identical to the one you uploaded.

I’d be glad to double-check with our development team if we can change this particular Markdown logic.

Please email us at support@crowdin.com and provide the following info:

  1. Your project ID (or project URL)
  2. The source file you’ve imported and the translation file you’ve exported as attachments to the email.
  3. The exact tool you’re working with (looks like this is Vitepress, so confirmation will be enough).

In the meantime, the Post Export Processor might offer a temporary solution to maintain the required formatting upon export.

5

Thanks very much @Dima - I will do so next week (and try the parser option)