godotengine/godot-docs-l10n
1
0
Fork 0
mirror of https://github.com/godotengine/godot-docs-l10n.git synced 2026-01-04 10:09:56 +03:00
Code Issues Packages Projects Releases Wiki Activity

Sync Sphinx and Weblate templates with current docs

Browse Source
This commit is contained in:
Rémi Verschelde
2020-09-28 16:17:30 +02:00
parent a86f0149ef
commit 05bccb6477
328 changed files with 8256 additions and 6867 deletions
Download Patch File Download Diff File Expand all files Collapse all files

20
sphinx/templates/development/compiling/compiling_for_web.pot
View File

@@ -6,9 +6,9 @@
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: Godot Engine latest\n"
"Project-Id-Version: Godot Engine 3.2\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2020-09-09 13:27+0200\n"
"POT-Creation-Date: 2020-09-28 16:14+0200\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
@@ -61,34 +61,34 @@ msgid "Open a terminal and navigate to the root directory of the engine source c
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:41
msgid "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be built into the engine. Since ``eval()`` calls can be a security concern, the ``javascript_eval`` option can be used to build without the singleton::"
msgid "By default, the :ref:`JavaScript singleton <doc_javascript_eval>` will be built into the engine. Official export templates also have the JavaScript singleton enabled. Since ``eval()`` calls can be a security concern, the ``javascript_eval`` option can be used to build without the singleton::"
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:48
#: ../../docs/development/compiling/compiling_for_web.rst:49
msgid "The engine will now be compiled to WebAssembly by Emscripten. Once finished, the resulting file will be placed in the ``bin`` subdirectory. Its name is ``godot.javascript.opt.zip`` for release or ``godot.javascript.opt.debug.zip`` for debug."
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:53
#: ../../docs/development/compiling/compiling_for_web.rst:54
msgid "Finally, rename the zip archive to ``webassembly_release.zip`` for the release template::"
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:58
#: ../../docs/development/compiling/compiling_for_web.rst:59
msgid "And ``webassembly_debug.zip`` for the debug template::"
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:63
#: ../../docs/development/compiling/compiling_for_web.rst:64
msgid "Building per asm.js translation or LLVM backend"
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:65
#: ../../docs/development/compiling/compiling_for_web.rst:66
msgid "WebAssembly can be compiled in two ways: The default is to first compile to asm.js, a highly optimizable subset of JavaScript, using Emscripten's *fastcomp* fork of LLVM. This code is then translated to WebAssembly using a tool called ``asm2wasm``. Emscripten automatically takes care of both processes, we simply run SCons."
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:71
#: ../../docs/development/compiling/compiling_for_web.rst:72
msgid "The other method uses LLVM's WebAssembly backend. This backend is available starting with LLVM 8 or in development builds. Emscripten manages this process as well, so we just invoke SCons."
msgstr ""
#: ../../docs/development/compiling/compiling_for_web.rst:75
#: ../../docs/development/compiling/compiling_for_web.rst:76
msgid "In order to choose one of the two methods, the ``LLVM_ROOT`` variable in the Emscripten configuration file is used. If it points to a directory containing binaries of Emscripten's *fastcomp* fork of clang, ``asm2wasm`` is used. This is the default in a normal Emscripten installation. Otherwise, LLVM binaries built with the WebAssembly backend will be expected and the LLVM's WebAssembly backend is used."
msgstr ""