varun-r-mallya/sysprof
1
0
Fork 0
mirror of https://github.com/varun-r-mallya/sysprof.git synced 2025-12-31 20:36:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

Updated Czech translation

Browse Source
This commit is contained in:
Marek Cernocky
2017-09-25 19:08:06 +02:00
parent 57b863129e
commit c572338746
1 changed files with 15 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
help/cs/cs.po
View File

@ -6,8 +6,8 @@
msgid ""
msgstr ""
"Project-Id-Version: sysprof master\n"
"POT-Creation-Date: 2017-06-28 17:59+0000\n"
"PO-Revision-Date: 2017-08-31 10:58+0200\n"
"POT-Creation-Date: 2017-09-25 16:15+0000\n"
"PO-Revision-Date: 2017-09-25 19:06+0200\n"
"Last-Translator: Marek Černocký <marek@manet.cz>\n"
"Language-Team: čeština <gnome-cs-list@gnome.org>\n"
"Language: cs\n"
@ -372,13 +372,18 @@ msgstr ""
"aplikace přešla do/z linuxového jádra. To se děje z různých důvodů, "
"například kvůli <em>systémovému volání</em> nebo <em>signálu</em>."
#. (itstool) path: page/title
#: C/faq.page:9
msgid "What does heap mean?"
msgstr "Co znamená heap?"
#. (itstool) path: section/title
#: C/faq.page:10
#: C/faq.page:12
msgid "What does \"In file [heap]\" mean?"
msgstr "Co znamená „In file [heap]“?"
#. (itstool) path: section/p
#: C/faq.page:12
#: C/faq.page:14
msgid ""
"This means that sysprof believes a function was called from somewhere in the "
"program's heap (where <code>malloc</code> allocates memory) rather than the "
@ -391,12 +396,12 @@ msgstr ""
"programu existuje několik vysvětlení."
#. (itstool) path: section/title
#: C/faq.page:19
#: C/faq.page:22
msgid "JIT (Just in Time) compilers"
msgstr "Kompilátory JIT (Just in Time)"
#. (itstool) path: section/p
#: C/faq.page:21
#: C/faq.page:24
msgid ""
"Languages like Java can generate executable code while a program is running "
"and store it in the heap. Sysprof is accurately reporting the situation in "
@ -406,12 +411,12 @@ msgstr ""
"ukládat jej na haldě. Sysprof v takovém případě situaci hlásí správně."
#. (itstool) path: section/title
#: C/faq.page:27
#: C/faq.page:30
msgid "Optimizing compilers"
msgstr "Optimalizující kompilátory"
#. (itstool) path: section/p
#: C/faq.page:29
#: C/faq.page:32
msgid ""
"C and C++ compilers can optimize away information needed to determine a "
"function's caller, so it is mistaken for [heap]. You can still tell how "
@ -422,7 +427,7 @@ msgstr ""
"říci, jak často jsou jednotlivé funkce programem volané, ale ne odkud."
#. (itstool) path: note/p
#: C/faq.page:35
#: C/faq.page:38
msgid ""
"For gcc, the flag <code>-fno-omit-frame-pointer</code> will prevent this "
"optimization. The flag is not always needed, for example on x86_64 machines "
@ -433,7 +438,7 @@ msgstr ""
"x86_64 je potřeba jen při optimalizaci -03."
#. (itstool) path: note/p
#: C/faq.page:41
#: C/faq.page:44
msgid ""
"To get the most detailed and accurate call tree from un-optimized code, use "
"these flags: <code>-ggdb -fno-omit-frame-pointer -O0</code>"