<html lang="en">
<head>
<title>HTML Beispieldatei</title>
<meta charset="UTF-8">
<link href="https://fonts.googleapis.com/css?family=Poppins:400,500" rel="stylesheet">
<link href="https://fonts.googleapis.com/css?family=Noto+Sans+KR:400,500&subset=korean" rel="stylesheet">
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<body>
<div class="header">
<h1>Crowdin HTML Beispiel</h1>
<p>Eine <b>responsive</b> Webseite wurde für Testzwecke erstellt.</p>
</div>
</body>
</html>Usually, in HTML files, texts enclosed in < and > entities don’t require translation and are treated by Crowdin as HTML tags. Depending on the HTML tags displaying option selected in the Editor settings, they might be displayed in a simplified version (e.g., <0>) in the Editor for translators’ convenience and copied into the translation. Although, occasionally, texts enclosed in < and > entities might require translation. In this case, as a possible way to proceed, you can replace < and > entities with the respective entity numbers (< for < and > for >) and update the source HTML files. As a result, translators will be able to see and translate the enclosed texts.