The Weblate Manual 2.6place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" Should the language definition for translation be missing, empty definition is created and named as “cs_CZ (generated)”. You should adjust the definition and report this back to Weblate authors so that missing0 码力 | 235 页 | 1009.42 KB | 1 年前3- The Weblate Manual 2.9place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 265 页 | 1.10 MB | 1 年前3
- The Weblate Manual 2.8place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 251 页 | 1.07 MB | 1 年前3
- The Weblate Manual 2.7place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" Should the language definition for translation be missing, empty definition is created and named as “cs_CZ (generated)”. You should adjust the definition and report this back to Weblate authors so that missing0 码力 | 242 页 | 1014.46 KB | 1 年前3
- The Weblate Manual 2.11place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 280 页 | 1.12 MB | 1 年前3
- The Weblate Manual 2.10.1place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 276 页 | 1.12 MB | 1 年前3
- The Weblate Manual 2.12place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 287 页 | 1.18 MB | 1 年前3
- The Weblate Manual 2.10place, we can start first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po has already some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 276 页 | 1.11 MB | 1 年前3
- The Weblate Manual 4.3.1we can start our first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po already has some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 664 页 | 9.34 MB | 1 年前3
- The Weblate Manual 4.2.1we can start our first translation: $ msginit -i po/hello.pot -l cs --no-translator -o po/cs.po Created cs.po. The just created cs.po already has some information filled in. Most importantly it got 2015-10-23 11:02+0200\n" "Last-Translator: Automatically generated\n" "Language-Team: none\n" "Language: cs\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=ASCII\n" "Content-Transfer-Encoding: 8bit\n" templates (this includes reordering the strings to match new template): $ msgmerge --previous --update po/cs.po po/hello.pot Importing to Weblate To import such translation into Weblate, all you need to define0 码力 | 639 页 | 9.32 MB | 1 年前3
共 298 条
- 1
- 2
- 3
- 4
- 5
- 6
- 30