Rachel AndrewThere's been a lot of discussion about masonry in CSS recently. I wrote about the Chrome team's proposal to help clarify why we have concerns with bundling masonry in with grid, and to show that a separate spec doesn't mean fewer features. https://developer.chrome.com/blog/masonry #css
Thomas Kräftner@rachelandrew I am not sure if the following critique is reaching the wrong person with you so excuse me if not. But the automatic translation to German of this post I got is such utter shit it would be way better to just have it in English only.
@rachelandrew Mostly because of the fact that all technical terms are translated in a literal and very cringe way. But also the rest of the language sounds very strange, somehow robotic and very unnatural.
@kraftner I'd suggest you switch to the English version then. Unfortunately we can't translate by hand all of our content into every language, so machine translation means that people who can't read the English version have something. Is it perfect? No. Is it better than nothing? We have data that shows it's appreciated by many people.
@rachelandrew Obviously I did that. Also sorry if my message was too harsh. In reading it again I could have phrased that better and more constructive: Maybe there is some way to at least mark some technical words like Masonry or Grid as untranslatable terms which would already greatly improve the output if that is possible technically.