You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When we do style changes or rework the layout of the site it can happen that the translated content drifts from the head. There may be different header depths, some css styling may not be applied. I have also encountered german translations where markdown markers were omitted entirely.
While we can probably catch some of these things manually it might be worth looking into whether we can detect structural differences between EN and translated content so that we can flag these strings for verification/correction.
I have looked into whether syntactic/structural analysis of markdown can be done but haven't found anything promising. Given that md files are converted into html before rendering, we might look into comparing the element trees of the rendered markdown fragments.
I know Lokalise has some features to highlight structural inconsistencies but it seems that it only captures html tags and doesn't fully take markdown syntax into account.
The text was updated successfully, but these errors were encountered:
I have been using this script to spot check markdown issues in newly launched languages and it seems to be helpful. I will need to document the best practices around using it in our processes and, ideally, see if we could also automatically integrate it with language PRs.
When we do style changes or rework the layout of the site it can happen that the translated content drifts from the head. There may be different header depths, some css styling may not be applied. I have also encountered german translations where markdown markers were omitted entirely.
While we can probably catch some of these things manually it might be worth looking into whether we can detect structural differences between EN and translated content so that we can flag these strings for verification/correction.
I have looked into whether syntactic/structural analysis of markdown can be done but haven't found anything promising. Given that md files are converted into html before rendering, we might look into comparing the element trees of the rendered markdown fragments.
I know Lokalise has some features to highlight structural inconsistencies but it seems that it only captures html tags and doesn't fully take markdown syntax into account.
The text was updated successfully, but these errors were encountered: