Skip to content

Commit

Permalink
Update po files
Browse files Browse the repository at this point in the history
  • Loading branch information
@bbhtt
bbhtt committed Feb 4, 2025
1 parent aafeb44 commit edf1532
Show file tree
Hide file tree
Showing 28 changed files with 1,531 additions and 691 deletions.
20 changes: 17 additions & 3 deletions po/de/LC_MESSAGES/debugging.po
View file
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Flatpak\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-12-03 21:11+0530\n"
"POT-Creation-Date: 2025-02-05 01:10+0530\n"
"PO-Revision-Date: 2018-05-20 10:36-0400\n"
"Last-Translator: Copied by Zanata <copied-by-zanata@zanata.org>\n"
"Language: de\n"
Expand Down Expand Up @@ -256,8 +256,8 @@ msgstr ""

#: ../../debugging.rst:183
msgid ""
"Session or system bus traffic can be audited by passing ``--log-session-"
"bus`` and ``--log-system-bus`` respectively to ``flatpak run``::"
"Session bus traffic can be audited by passing ``--log-session-bus`` to "
"``flatpak run``::"
msgstr ""

#: ../../debugging.rst:188
Expand All @@ -267,6 +267,13 @@ msgid ""
"required::"
msgstr ""

#: ../../debugging.rst:194
msgid ""
"Similarly, system bus traffic can be audited by passing ``--log-system-"
"bus`` to ``flatpak run``. This also requires a system bus name to be "
"present in the permissions. If not a bogus bus name can be passed::"
msgstr ""

#~ msgid "Running debugging tools"
#~ msgstr ""

Expand Down Expand Up @@ -358,3 +365,10 @@ msgstr ""
#~ "names`` or ``--own-names`` required::"
#~ msgstr ""

#~ msgid ""
#~ "Session or system bus traffic can "
#~ "be audited by passing ``--log-"
#~ "session-bus`` and ``--log-system-bus`` "
#~ "respectively to ``flatpak run``::"
#~ msgstr ""

94 changes: 58 additions & 36 deletions po/de/LC_MESSAGES/electron.po
View file
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ msgid ""
msgstr ""
"Project-Id-Version: Flatpak \n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2024-09-26 16:32-0300\n"
"POT-Creation-Date: 2025-02-05 01:10+0530\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"
Expand Down Expand Up @@ -156,40 +156,41 @@ msgid ""
"access."
msgstr ""

#: ../../electron.rst:126
#: ../../electron.rst:127
msgid ""
"Native wayland support in electron is experimental and often unstable. It"
" is advised to stick with the X11 and Xwayland configuration above as the"
" default."
msgstr ""

#: ../../electron.rst:130
#: ../../electron.rst:131
msgid ""
"To enable experimental `native Wayland` support in Electron>=20, the "
"``--ozone-platform-hint=auto`` flag can be passed to the program. `auto` "
"will choose Wayland when the session is wayland and Xwayland or X11 "
"otherwise."
msgstr ""

#: ../../electron.rst:135
#: ../../electron.rst:136
msgid ""
"The recommended option is to leave it to the user. So ``--socket=x11`` "
"should be used in manifest and Wayland can be tested with::"
msgstr ""

#: ../../electron.rst:140
#: ../../electron.rst:141
msgid ""
"To make native wayland the `default` for users ``--socket=fallback-x11`` "
"and ``--socket=wayland`` must be used in the manifest."
msgstr ""

#: ../../electron.rst:143
#: ../../electron.rst:144
msgid ""
"Client-side window decorations in native wayland can be enabled by "
"passing ``--enable-features=WaylandWindowDecorations`` (Electron>=17)."
"For Electron versions between 17 and 27, client-side window decorations "
"in native wayland can be enabled by passing ``--enable-"
"features=WaylandWindowDecorations``."
msgstr ""

#: ../../electron.rst:146
#: ../../electron.rst:147
msgid ""
"Electron uses ``libnotify`` on Linux to provide desktop notifications. "
"libnotify `since 0.8.0 "
Expand All @@ -200,17 +201,17 @@ msgid ""
"name=org.freedesktop.Notifications`` is not required."
msgstr ""

#: ../../electron.rst:152
#: ../../electron.rst:153
msgid ""
"``org.electronjs.Electron2.BaseApp`` since ``branch/23.08`` comes with "
"``libnotify>=0.8.0``"
msgstr ""

#: ../../electron.rst:158
#: ../../electron.rst:159
msgid "Using correct desktop file name"
msgstr ""

#: ../../electron.rst:160
#: ../../electron.rst:161
msgid ""
"It's important for Linux applications to set the correct desktop file "
"name. If not, it can lead to problems like missing the window icon under "
Expand All @@ -221,7 +222,7 @@ msgid ""
"\"com.example.MyApp.desktop\"``."
msgstr ""

#: ../../electron.rst:164
#: ../../electron.rst:165
msgid ""
"In case you repack a binary, you can use the ``patch-desktop-filename`` "
"script provided by the BaseApp. Each Electron binary ships with "
Expand All @@ -231,30 +232,30 @@ msgid ""
"${FLATPAK_DEST}/my-app/resources/app.asar``."
msgstr ""

#: ../../electron.rst:169
#: ../../electron.rst:170
msgid "Build options"
msgstr ""

#: ../../electron.rst:171
#: ../../electron.rst:172
msgid ""
"These build options aren't strictly necessary, but can be useful if "
"something goes wrong. ``env`` allows setting an array of environment "
"variables, in this case we set ``NPM_CONFIG_LOGLEVEL`` to ``info`` so "
"that ``npm`` gives us more detailed error messages."
msgstr ""

#: ../../electron.rst:187
#: ../../electron.rst:188
msgid "The application module"
msgstr ""

#: ../../electron.rst:189
#: ../../electron.rst:190
msgid ""
"The final section of the manifest defines how the application module "
"should be built. This is where some of the additional logic for Electron "
"and Node.js can be found."
msgstr ""

#: ../../electron.rst:193
#: ../../electron.rst:194
msgid ""
"By default, ``flatpak-builder`` doesn't allow build tools to access the "
"network. This means that tools which rely on downloading sources will not"
Expand All @@ -263,23 +264,23 @@ msgid ""
"means that these will be found when it comes to the build."
msgstr ""

#: ../../electron.rst:199
#: ../../electron.rst:200
msgid ""
"The next part of the manifest describes how the application should be "
"built. The simple buildsystem option is used, which allows a sequence of "
"commands to be specified, which are used for the build. The download "
"location and hash of the application are also specified."
msgstr ""

#: ../../electron.rst:222
#: ../../electron.rst:223
msgid "Bundling NPM packages"
msgstr ""

#: ../../electron.rst:224
#: ../../electron.rst:225
msgid "The next line is how NPM modules get bundled as part of Flatpaks:"
msgstr ""

#: ../../electron.rst:230
#: ../../electron.rst:231
msgid ""
"Since even simple Node.js applications depend on dozens of packages, it "
"would be impractical to specify all of them as part of a manifest file. A"
Expand All @@ -289,7 +290,7 @@ msgid ""
"sources."
msgstr ""

#: ../../electron.rst:236
#: ../../electron.rst:237
msgid ""
"The Python script requires a ``package-lock.json`` (or ``yarn.lock``) "
"file. This file contains information about the packages that an "
Expand All @@ -298,7 +299,7 @@ msgid ""
" then run as follows::"
msgstr ""

#: ../../electron.rst:243
#: ../../electron.rst:244
msgid ""
"This generates the manifest JSON needed to build the NPM/Yarn packages "
"for the application, which are outputted to a file called ``generated-"
Expand All @@ -309,22 +310,22 @@ msgid ""
"above."
msgstr ""

#: ../../electron.rst:251
#: ../../electron.rst:252
msgid "Launching the app"
msgstr ""

#: ../../electron.rst:253
#: ../../electron.rst:254
msgid ""
"The Electron app is run through a simple script. This can be given any "
"name but must be specified in the manifest's ``\"command\":`` property. "
"See below a sample wrapper for launching app:"
msgstr ""

#: ../../electron.rst:265
#: ../../electron.rst:266
msgid "Build commands"
msgstr ""

#: ../../electron.rst:267
#: ../../electron.rst:268
msgid ""
"Last but not least, since the simple build option is being used, a list "
"of build commands must be provided. As can be seen, ``npm`` is run with "
Expand All @@ -334,7 +335,7 @@ msgid ""
"``/app/bin/`` so that it will be on ``$PATH``:"
msgstr ""

#: ../../electron.rst:289
#: ../../electron.rst:290
msgid ""
"Note that if the application you are trying to package contains a "
"``build`` block in ``package.json`` with instructions for Linux, this can"
Expand All @@ -343,18 +344,18 @@ msgid ""
"configuration that will try to download AppImage binaries:"
msgstr ""

#: ../../electron.rst:299
#: ../../electron.rst:300
msgid ""
"The preferred way of fixing this, is not a patch, but a build-time edit "
"using ``jq``. The following command will replace ``\"target\": "
"\"AppImage\"`` with ``\"target\": \"dir\"``:"
msgstr ""

#: ../../electron.rst:306
#: ../../electron.rst:307
msgid "Make setProgressBar and setBadgeCount work"
msgstr ""

#: ../../electron.rst:307
#: ../../electron.rst:308
msgid ""
"The `setProgressBar <https://www.electronjs.org/docs/latest/api/browser-"
"window#winsetprogressbarprogress-options>`_ and `setBadgeCount "
Expand All @@ -368,12 +369,13 @@ msgid ""
"extension and `Plank <https://launchpad.net/plank>`_."
msgstr ""

#: ../../electron.rst:310
#: ../../electron.rst:311
msgid ""
"To make it work in Flatpak, the app needs to :ref:`use the correct "
"desktop filename <use-correct-desktop-filename>`. The Flatpak also needs "
"the ``--talk-name=com.canonical.Unity`` permission. Electron versions "
"earlier than v32 checks `checks if it's running on Unity or KDE "
"desktop filename <use-correct-desktop-filename>` in its embedded "
"`package.json` file. The Flatpak also needs the ``--talk-"
"name=com.canonical.Unity`` permission. Electron versions earlier than v32"
" checks `checks if it's running on Unity or KDE "
"<https://github.com/electron/electron/blob/fb88375ab4d2161dbf7e958a2a94c7c6d97dc84c/shell/browser/linux/unity_service.cc#L64>`_"
" before using the UnityLauncherAPI."
msgstr ""
Expand Down Expand Up @@ -432,3 +434,23 @@ msgstr ""
#~ "for sound and enables network access:"
#~ msgstr ""

#~ msgid ""
#~ "Client-side window decorations in native"
#~ " wayland can be enabled by passing"
#~ " ``--enable-features=WaylandWindowDecorations`` "
#~ "(Electron>=17)."
#~ msgstr ""

#~ msgid ""
#~ "To make it work in Flatpak, the"
#~ " app needs to :ref:`use the correct"
#~ " desktop filename <use-correct-desktop-"
#~ "filename>`. The Flatpak also needs the"
#~ " ``--talk-name=com.canonical.Unity`` permission. "
#~ "Electron versions earlier than v32 "
#~ "checks `checks if it's running on "
#~ "Unity or KDE "
#~ "<https://github.com/electron/electron/blob/fb88375ab4d2161dbf7e958a2a94c7c6d97dc84c/shell/browser/linux/unity_service.cc#L64>`_"
#~ " before using the UnityLauncherAPI."
#~ msgstr ""

Loading

0 comments on commit edf1532

Please sign in to comment.