manuskript/i18n/manuskript_uk.ts

4661 lines
180 KiB
TypeScript
Raw Normal View History

<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE TS>
<TS version="2.1" language="uk">
<context>
<name>Export</name>
<message>
<location filename="../manuskript/exporter/manuskript/HTML.py" line="18"/>
<source>Basic HTML output using the Python module 'markdown'.</source>
<translation type="unfinished">Звичайний вивід HTML з уживанням модуля Python 'markdown'.</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/HTML.py" line="19"/>
<source>Python module 'markdown'.</source>
<translation type="unfinished">Модуль Python 'markdown'.</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/HTML.py" line="54"/>
<source>Markdown source</source>
<translation>Вихідний код на Markdown</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/HTML.py" line="55"/>
<source>HTML Source</source>
<translation>Вихідний код на HTML</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/HTML.py" line="59"/>
<source>HTML Output</source>
<translation>Вивід HTML</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/__init__.py" line="15"/>
<source>Default exporter, provides basic formats used by other exporters.</source>
<translation>Типовий експортер, надає базові формати, що їх уживають інші експортери.</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/markdown.py" line="60"/>
<source>Preview with highlighter.</source>
<translation>Попередній перегляд із маркером.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/manuskript/plainText.py" line="17"/>
<source>Plain text</source>
<translation>Звичайний текст</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/HTML.py" line="13"/>
<source>A little known format modestly used. You know, web sites for example.</source>
<translation>Маловідомий і зрідка використовуваний формат. Якісь там веб-сайти, велике диво.</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/PDF.py" line="18"/>
<source>Needs LaTeX to be installed.</source>
<translation type="unfinished">LaTeX має бути встановлено.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/converters/pandocConverter.py" line="76"/>
<source>Error</source>
<translation>Помилка</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="96"/>
<source>Standalone document (not just a fragment)</source>
<translation>Окремий документ (не лише фрагмент)</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="99"/>
<source>Include a table of contents.</source>
<translation>Включити зміст.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="102"/>
<source>Number of sections level to include in TOC: </source>
<translation>Рівень підрозділів, що їх буде додано до змісту: </translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="106"/>
<source>Typographically correct output</source>
<translation>Виправити результат для друку</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="109"/>
<source>Normalize the document (cleaner)</source>
<translation>Чистіший документ (виправити помилки)</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="111"/>
<source>Specify the base level for headers: </source>
<translation>Укажіть початковий рівень заголовків: </translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="118"/>
<source>Use reference-style links instead of inline links</source>
<translation>Використувати виноски замість вбудованих посилань</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="120"/>
<source>Use ATX-style headers</source>
<translation>Використувати atx-заголовки (# ґратки)</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="124"/>
<source>Use &lt;q&gt; tags for quotes in HTML</source>
<translation>Використувати тег &lt;p&gt; для цитувань у HTML</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="131"/>
<source>LaTeX engine used to produce the PDF.</source>
<translation>Рушій LaTeX для створення файлу PDF.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="141"/>
<source>Paper size:</source>
<translation>Формат аркуша:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="144"/>
<source>Font size:</source>
<translation>Розмір шрифту:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="147"/>
<source>Class:</source>
<translation>Клас:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="150"/>
<source>Line spacing:</source>
<translation>Міжрядковий інтервал:</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/outputFormats.py" line="10"/>
<source>Books that don't kill trees.</source>
<translation>Книжки, що вони не вбивають дерева.</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/outputFormats.py" line="21"/>
<source>OpenDocument format. Used by LibreOffice for example.</source>
<translation>Формат OpenDocument. Наприклад, ним користується LibreOffice.</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/outputFormats.py" line="32"/>
<source>Microsoft Office (.docx) document.</source>
<translation>Документ Microsoft Office (.docx).</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/plainText.py" line="22"/>
<source>reStructuredText is a lightweight markup language.</source>
<translation type="unfinished">reStructuredText є полегшеною мовою розмітки даних...</translation>
</message>
<message>
<location filename="../manuskript/exporter/manuskript/markdown.py" line="14"/>
<source>Just like plain text, excepts adds markdown titles.
Presupposes that texts are formatted in markdown.</source>
<translation>Схожа на звичайний текст, але надає заголовки markdown.
Припускає, що текст форматовано на markdown.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/manuskript/plainText.py" line="18"/>
<source>Simplest export to plain text. Allows you to use your own markup not understood
by Manuskript, for example &lt;a href='www.fountain.io'&gt;Fountain&lt;/a&gt;.</source>
<translation type="unfinished">Найпростіший експорт у звичайний текст. Дозволяє використувати власні мови розмітки, що їх не підтримує
manuskript, наприклад &lt;a href='www.fountain.io'&gt;Fountain&lt;/a&gt;.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/__init__.py" line="22"/>
<source>&lt;p&gt;A universal document converter. Can be used to convert Markdown to a wide range of other
formats.&lt;/p&gt;
&lt;p&gt;Website: &lt;a href="http://www.pandoc.org"&gt;http://pandoc.org/&lt;/a&gt;&lt;/p&gt;
</source>
<translation type="unfinished">&lt;p&gt;Загальний конвертер документів. Ним можна конвертувати markdown у безліч інших
форматів.&lt;/p&gt;
&lt;p&gt;Сторінка: &lt;a href="http://www.pandoc.org"&gt;http://pandoc.org/&lt;/a&gt;&lt;/p&gt;
</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/PDF.py" line="19"/>
<source>a valid LaTeX installation. Pandoc recommendations can be found on:
&lt;a href="https://pandoc.org/installing.html"&gt;pandoc.org/installing.html&lt;/a&gt;. If you want Unicode support, you need XeLaTeX.</source>
<translation type="unfinished">встановлений робочий дистрибутив LaTeX. Перевірте рекомендації pandoc на:
&lt;a href="http://pandoc.org/installing.html"&gt;http://pandoc.org/installing.html&lt;/a&gt;. Якщо ви потребуєте підтримки unicode, оберіть xelatex.</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/plainText.py" line="10"/>
<source>Export to markdown, using pandoc. Allows more formatting options
than the basic manuskript exporter.</source>
<translation>Експорт у markdown за допомогою pandoc. Надає більше можливостей форматування,
ніж загальний експортер.</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/plainText.py" line="33"/>
<source>LaTeX is a word processor and document markup language used to create
beautiful documents.</source>
<translation>LaTeX - це текстовий процесор і мова розмітки даних для створення
гарних документів.</translation>
</message>
<message>
<location filename="../manuskript/exporter/pandoc/plainText.py" line="45"/>
<source>The purpose of this format is to provide a way to exchange information
between outliners and Internet services that can be browsed or controlled
through an outliner.</source>
<translation>Цей формат призначений на обмін інформацією
між структуризаторами та інтернет-службами, які можна переглядати чи контролювати
за допомогою структуризатора.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="114"/>
<source>Disable YAML metadata block.
Use that if you get YAML related error.</source>
<translation>Вимкнути блок метаданих YAML.
Оберіть у разі помилки з YAML.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="134"/>
<source>Convert to ePUB3</source>
<translation>Конвертувати у ePUB3</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="122"/>
<source>Self-contained HTML files, with no dependencies</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/manuskript/plainText.py" line="51"/>
<source>Could not process regular expression:
{}</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/manuskript/plainText.py" line="71"/>
<source>Choose output file…</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>ExportersManager</name>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="14"/>
<source>Manage Exporters</source>
<translation>Керувати експортерами</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="21"/>
<source>Manuskript</source>
<translation>Манускрипт</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="66"/>
<source>Description</source>
<translation>Опис</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="100"/>
<source>Offers export to</source>
<translation>Може експортувати у</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="184"/>
<source>Status</source>
<translation>Стан</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="190"/>
<source>Status:</source>
<translation>Стан:</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="210"/>
<source>Version:</source>
<translation>Версія:</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="233"/>
<source>Path:</source>
<translation>Шлях:</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="258"/>
<source>...</source>
<translation>...</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager_ui.ui" line="273"/>
<source>{HelpText}</source>
<translation>{ТекстДовідки}</translation>
</message>
</context>
<context>
<name>FrequencyAnalyzer</name>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="14"/>
<source>Frequency Analyzer</source>
<translation>Частотний аналіз</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="24"/>
<source>Word frequency</source>
<translation>Частота слів</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="37"/>
<source>Settings</source>
<translation>Налаштування</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="49"/>
<source>Minimum size:</source>
<translation>Мінімальний розмір:</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="63"/>
<source>Exclude words (comma separated):</source>
<translation type="unfinished">Не враховувати слова (розділені комою):</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="156"/>
<source>Analyze</source>
<translation>Аналізувати</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="107"/>
<source>Phrase frequency</source>
<translation>Частота висловів</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="115"/>
<source>Number of words: from</source>
<translation>Кількість слів: від</translation>
</message>
<message>
<location filename="../manuskript/ui/tools/frequency_ui.ui" line="129"/>
<source>to</source>
<translation>до</translation>
</message>
</context>
<context>
<name>Import</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/markdownImporter.py" line="175"/>
<source>Markdown import</source>
<translation>Імпортувати файл markdown</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/markdownImporter.py" line="179"/>
<source>&lt;b&gt;Info:&lt;/b&gt; A very simple
parser that will go through a markdown document and
create items for each titles.&lt;br/&gt;&amp;nbsp;</source>
<translation>&amp;lt;b&amp;gt;Інфо:&amp;lt;/b&amp;gt; Дуже простий
аналізатор, який пройде документом markdown і
створить елементи на кожний заголовок.&amp;lt;br/&amp;gt;&amp;nbsp;</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/folderImporter.py" line="96"/>
<source>Folder import</source>
<translation>Імпорт теки</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/folderImporter.py" line="100"/>
<source>&lt;p&gt;&lt;b&gt;Info:&lt;/b&gt; Imports a whole
directory structure. Folders are added as folders, and
plaintext documents within (you chose which ones by extension)
are added as scene.&lt;/p&gt;
&lt;p&gt;Only text files are supported (not images, binary or others).&lt;/p&gt;</source>
<translation>&lt;p&gt;&lt;b&gt;Інфо:&lt;/b&gt; Імпортує
структуру тек цілком. Теки буде додано як теки, а
внутрішні документи звичайного тексту (ви обираєте, які саме за типом файлу)
як сцени.&lt;/p&gt;
&lt;p&gt;Підтримувано лише текстові файли, а не зображення, двійкові тощо.&lt;/p&gt;</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/folderImporter.py" line="107"/>
<source>Include only those extensions:</source>
<translation>Включити лише наступні розширення:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/folderImporter.py" line="107"/>
<source>Comma separated values</source>
<translation type="unfinished">Значення, розділені комою</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/folderImporter.py" line="112"/>
<source>Sort items by name</source>
<translation>Сортувати елементи за назвою</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/folderImporter.py" line="116"/>
<source>Import folder then files</source>
<translation>Імпортувати теку і файли</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/opmlImporter.py" line="64"/>
<source>OPML Import</source>
<translation>Імпорт OPML</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/opmlImporter.py" line="36"/>
<source>File open failed.</source>
<translation>Не вдалося відкрити файл.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/opmlImporter.py" line="64"/>
<source>This does not appear to be a valid OPML file.</source>
<translation>Здається, це не припустимий файл OPML.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/pandocImporters.py" line="57"/>
<source>Pandoc import</source>
<translation>Імпорт pandoc</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/pandocImporters.py" line="60"/>
<source>&lt;b&gt;Info:&lt;/b&gt; Manuskript can
import from &lt;b&gt;markdown&lt;/b&gt; or &lt;b&gt;OPML&lt;/b&gt;. Pandoc will
convert your document to either (see option below), and
then it will be imported in manuskript. One or the other
might give better result depending on your document.
&lt;br/&gt;&amp;nbsp;</source>
<translation>&amp;lt;b&amp;gt;Info:&amp;lt;/b&amp;gt; Манускрипт може
імпортувати з &amp;lt;b&amp;gt;markdown&amp;lt;/b&amp;gt; чи &amp;lt;b&amp;gt;OPML&amp;lt;/b&amp;gt;. Pandoc
конвертує ваш документ у будь-який з них (див. параметри), і
імпортує результат у Манускрипт. Один із двох
може дати кращий результат залежно від джерельного документу.
&amp;lt;br/&amp;gt;&amp;nbsp;</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/pandocImporters.py" line="68"/>
<source>Import using:</source>
<translation>Імпорт за допомогою:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/pandocImporters.py" line="72"/>
<source>Wrap lines:</source>
<translation>Переносити рядки:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/pandocImporters.py" line="72"/>
<source>&lt;p&gt;Should pandoc create
cosmetic / non-semantic line-breaks?&lt;/p&gt;&lt;p&gt;
&lt;b&gt;auto&lt;/b&gt;: wraps at 72 characters.&lt;br&gt;
&lt;b&gt;none&lt;/b&gt;: no line wrap.&lt;br&gt;
&lt;b&gt;preserve&lt;/b&gt;: tries to preserves line wrap from the
original document.&lt;/p&gt;</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/mindMapImporter.py" line="55"/>
<source>Mind Map Import</source>
<translation>Імпорт мапи думок</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/mindMapImporter.py" line="55"/>
<source>This does not appear to be a valid Mind Map file.</source>
<translation>Це не припустимий формат файлу мапи думок.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/mindMapImporter.py" line="70"/>
<source>Mind Map import</source>
<translation>Імпорт мапи думок</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/mindMapImporter.py" line="73"/>
<source>Import tip as:</source>
<translation>Імпортувати поради як:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/importer/mindMapImporter.py" line="89"/>
<source>Untitled</source>
<translation>Без назви</translation>
</message>
</context>
<context>
<name>MDEditCompleter</name>
<message>
<location filename="../manuskript/ui/views/MDEditCompleter.py" line="73"/>
<source>Insert reference</source>
<translation>Вставити посилання</translation>
</message>
</context>
<context>
<name>MainWindow</name>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1647"/>
<source>General</source>
<translation>Загальне</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="169"/>
<source>Title</source>
<translation>Назва</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="179"/>
<source>Subtitle</source>
<translation>Підзаголовок</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="189"/>
<source>Series</source>
<translation>Серія</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="199"/>
<source>Volume</source>
<translation>Том</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="226"/>
<source>Genre</source>
<translation>Жанр</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="236"/>
<source>License</source>
<translation>Ліцензія</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="249"/>
<source>Author</source>
<translation>Автор</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1656"/>
<source>Name</source>
<translation>Ім'я</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="277"/>
<source>Email</source>
<translation>Електронна пошта</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1442"/>
<source>Summary</source>
<translation>Стислий переказ</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="322"/>
<source>Situation:</source>
<translation>Ситуація:</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1357"/>
<source>Summary:</source>
<translation>Стислий переказ:</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="345"/>
<source>One sentence</source>
<translation>Одне речення</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1455"/>
<source>One paragraph</source>
<translation>Один абзац</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1460"/>
<source>One page</source>
<translation>Одна сторінка</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1465"/>
<source>Full</source>
<translation>Цілком</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="420"/>
<source>One sentence summary</source>
<translation>Переказ одним реченням</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="502"/>
<source>One paragraph summary</source>
<translation>Переказ одним абзацом</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="540"/>
<source>Expand each sentence of your one paragraph summary to a paragraph</source>
<translation>Розвиньте до абзацу кожне речення з вашого переказу одним абзацом</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="565"/>
<source>One page summary</source>
<translation>Переказ однією сторінкою</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="590"/>
<source>Full summary</source>
<translation>Загальний опис</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1094"/>
<source>Next</source>
<translation>Далі</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="676"/>
<source>What if...?</source>
<translation>Що як...?</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="688"/>
<source>Characters</source>
<translation>Персонажі</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="713"/>
<source>Names</source>
<translation>Імена</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1607"/>
<source>Filter</source>
<translation>Фільтрувати</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1203"/>
<source>Basic info</source>
<translation>Загальна інформація</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1222"/>
<source>Importance</source>
<translation>Значність</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="880"/>
<source>Motivation</source>
<translation>Мотивація</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="890"/>
<source>Goal</source>
<translation>Мета</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="900"/>
<source>Conflict</source>
<translation>Конфлікт</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="910"/>
<source>Epiphany</source>
<translation>Прояснення</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="920"/>
<source>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p align="right"&gt;One sentence&lt;br/&gt;summary&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</source>
<translation>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p align="right"&gt;Переказ одним&lt;br/&gt;реченням&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="930"/>
<source>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p align="right"&gt;One paragraph&lt;br/&gt;summary&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</source>
<translation>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p align="right"&gt;Переказ одним&lt;br/&gt;абзацом&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1021"/>
<source>Notes</source>
<translation>Нотатки</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1031"/>
<source>Detailed info</source>
<translation>Докладна інформація</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2041"/>
<source>Plots</source>
<translation>Сюжети</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1212"/>
<source>Plot</source>
<translation>Сюжет</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1229"/>
<source>Character(s)</source>
<translation>Персонаж(-і)</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1666"/>
<source>Description</source>
<translation>Опис</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1243"/>
<source>Result</source>
<translation>Результат</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1335"/>
<source>Resolution steps</source>
<translation>Кроки розвитку сюжету</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2065"/>
<source>World</source>
<translation>Світ</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1620"/>
<source>Populates with empty data</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1677"/>
<source>More</source>
<translation>Більше</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1686"/>
<source>Source of passion</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1696"/>
<source>Source of conflict</source>
<translation>Джерело конфлікту</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1554"/>
<source>Outline</source>
<translation>Обрис</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1874"/>
<source>Editor</source>
<translation>Редактор</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2005"/>
<source>Debug</source>
<translation>Налагодити</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2018"/>
<source>FlatData</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2028"/>
<source>Persos</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2089"/>
<source>Labels</source>
<translation>Позначки</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2123"/>
<source>&amp;File</source>
<translation>&amp;Файл</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2127"/>
<source>&amp;Recent</source>
<translation>&amp;Нещодавні</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="2147"/>
<source>&amp;Help</source>
<translation>&amp;Допомога</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2158"/>
<source>&amp;Tools</source>
<translation>&amp;Знаряддя</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2165"/>
<source>&amp;Edit</source>
<translation>&amp;Редагувати</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2221"/>
<source>&amp;View</source>
<translation>&amp;Переглянути</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2225"/>
<source>&amp;Mode</source>
<translation>&amp;Режим</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2254"/>
<source>&amp;Cheat sheet</source>
<translation>&amp;Шпаргалка</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2288"/>
<source>Sea&amp;rch</source>
<translation>Шука&amp;ти</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2325"/>
<source>&amp;Navigation</source>
<translation>&amp;Перехід</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2360"/>
<source>&amp;Open</source>
<translation>&amp;Відкрити</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2363"/>
<source>Ctrl+O</source>
<translation>Ctrl+O</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2372"/>
<source>&amp;Save</source>
<translation>&amp;Зберегти</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2375"/>
<source>Ctrl+S</source>
<translation>Ctrl+S</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2384"/>
<source>Sa&amp;ve as...</source>
<translation>Збере&amp;гти як...</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2387"/>
<source>Ctrl+Shift+S</source>
<translation>Ctrl+Shift+S</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2396"/>
<source>&amp;Quit</source>
<translation>&amp;Вихід</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2399"/>
<source>Ctrl+Q</source>
<translation>Ctrl+Q</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2414"/>
<source>&amp;Show help texts</source>
<translation>&amp;Показувати тексти довідки</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2417"/>
<source>Ctrl+Shift+B</source>
<translation>Ctrl+Shift+B</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2432"/>
<source>&amp;Spellcheck</source>
<translation>&amp;Перевірка правопису</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2435"/>
<source>F9</source>
<translation>F9</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2444"/>
<source>&amp;Labels...</source>
<translation>&amp;Позначки...</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2453"/>
<source>&amp;Status...</source>
<translation>&amp;Стан...</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1552"/>
<source>Tree</source>
<translation>Дерево</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2469"/>
<source>&amp;Simple</source>
<translation>&amp;Простий</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2477"/>
<source>&amp;Fiction</source>
<translation>&amp;Художня література</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1553"/>
<source>Index cards</source>
<translation>Каталог</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2496"/>
<source>S&amp;ettings</source>
<translation>Н&amp;алаштування</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2499"/>
<source>F8</source>
<translation>F8</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2508"/>
<source>&amp;Close project</source>
<translation>&amp;Закрити проєкт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2517"/>
<source>Co&amp;mpile</source>
<translation>Екс&amp;портувати</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2520"/>
<source>F6</source>
<translation>F6</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2525"/>
<source>&amp;Frequency Analyzer</source>
<translation>&amp;Частотний аналізатор</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="154"/>
<source>Book information</source>
<translation>Інформація про книжку</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2534"/>
<source>&amp;About</source>
<translation>&amp;Про програму</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2537"/>
<source>About Manuskript</source>
<translation>Про Манускрипт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="746"/>
<source>Manuskript</source>
<translation>Манускрипт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="872"/>
<source>Project {} saved.</source>
<translation>Проєкт {} збережено.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="876"/>
<source>WARNING: Project {} not saved.</source>
<translation>УВАГА: Проєкт {} не збережено.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="896"/>
<source>Project {} loaded.</source>
<translation>Проєкт {} завантажено.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="902"/>
<source>Project {} loaded with some errors.</source>
<translation>Проєкт {} завантажено з кількома помилками.</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1280"/>
<source> (~{} pages)</source>
<translation> (~{} сторінок)</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1283"/>
<source>Words: {}{}</source>
<translation>Слів: {}{}</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1291"/>
<source>Book summary</source>
<translation>Стислий переказ книжки</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1292"/>
<source>Project tree</source>
<translation>Дерево проєкту</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1293"/>
<source>Metadata</source>
<translation>Метадані</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1294"/>
<source>Story line</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1359"/>
<source>Enter information about your book, and yourself.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1362"/>
<source>The basic situation, in the form of a 'What if...?' question. Ex: 'What if the most dangerous
evil wizard wasn't able to kill a baby?' (Harry Potter)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1367"/>
<source>Take time to think about a one sentence (~50 words) summary of your book. Then expand it to
a paragraph, then to a page, then to a full summary.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1372"/>
<source>Create your characters.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1375"/>
<source>Develop plots.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1378"/>
<source>Build worlds. Create hierarchy of broad categories down to specific details.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1381"/>
<source>Create the outline of your masterpiece.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1384"/>
<source>Write.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1387"/>
<source>Debug info. Sometimes useful.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1401"/>
<source>Dictionary</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1544"/>
<source>Nothing</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1545"/>
<source>POV</source>
<translation>З погляду</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1546"/>
<source>Label</source>
<translation>Позначка</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1547"/>
<source>Progress</source>
<translation>Стан</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1548"/>
<source>Compile</source>
<translation>Експорт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1571"/>
<source>Icon color</source>
<translation>Колір позначки</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1572"/>
<source>Text color</source>
<translation>Колір тексту</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1573"/>
<source>Background color</source>
<translation>Колір тла</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1564"/>
<source>Icon</source>
<translation>Значок</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1565"/>
<source>Text</source>
<translation>Текст</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1566"/>
<source>Background</source>
<translation>Тло</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1567"/>
<source>Border</source>
<translation>Рамка</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1568"/>
<source>Corner</source>
<translation>Кут</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1371"/>
<source>Add plot step</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2546"/>
<source>&amp;Import</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2549"/>
<source>F7</source>
<translation type="unfinished">F7</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2558"/>
<source>&amp;Copy</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2561"/>
<source>Ctrl+C</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2570"/>
<source>C&amp;ut</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2573"/>
<source>Ctrl+X</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2582"/>
<source>&amp;Paste</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2585"/>
<source>Ctrl+V</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2594"/>
<source>&amp;Split</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2597"/>
<source>Ctrl+Shift+K</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2606"/>
<source>Sp&amp;lit at cursor</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2609"/>
<source>Ctrl+K</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2621"/>
<source>Ctrl+M</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2824"/>
<source>Ctrl+D</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2642"/>
<source>Del</source>
<translation>Вилучити</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2651"/>
<source>&amp;Move Up</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2654"/>
<source>Ctrl+Shift+Up</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2663"/>
<source>M&amp;ove Down</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2666"/>
<source>Ctrl+Shift+Down</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2630"/>
<source>Dupl&amp;icate</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2639"/>
<source>&amp;Delete</source>
<translation>&amp;Вилучити</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2675"/>
<source>&amp;Rename</source>
<translation>&amp;Перейменувати</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2678"/>
<source>F2</source>
<translation type="unfinished">F2</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2235"/>
<source>Organi&amp;ze</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2618"/>
<source>M&amp;erge</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/mainWindow.ui" line="1388"/>
<source>Remove selected plot step(s)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2169"/>
<source>&amp;Format</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2177"/>
<source>&amp;Header</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2683"/>
<source>&amp;Level 1 (setext)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2686"/>
<source>Ctrl+Alt+1</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2691"/>
<source>Level &amp;2</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2694"/>
<source>Ctrl+Alt+2</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2699"/>
<source>Level &amp;1 (atx)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2702"/>
<source>Ctrl+1</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2707"/>
<source>L&amp;evel 2</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2710"/>
<source>Ctrl+2</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2715"/>
<source>Level &amp;3</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2718"/>
<source>Ctrl+3</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2723"/>
<source>Level &amp;4</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2726"/>
<source>Ctrl+4</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2731"/>
<source>Level &amp;5</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2734"/>
<source>Ctrl+5</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2739"/>
<source>Level &amp;6</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2742"/>
<source>Ctrl+6</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2751"/>
<source>&amp;Bold</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2754"/>
<source>Ctrl+B</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2763"/>
<source>&amp;Italic</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2766"/>
<source>Ctrl+I</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2775"/>
<source>&amp;Strike</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2780"/>
<source>&amp;Verbatim</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2785"/>
<source>Su&amp;perscript</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2788"/>
<source>Ctrl++</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2793"/>
<source>Subsc&amp;ript</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2796"/>
<source>Ctrl+-</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2801"/>
<source>Co&amp;mment block</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2804"/>
<source>Ctrl+Shift+C</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2813"/>
<source>Clear &amp;formats</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2816"/>
<source>Ctrl+0</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2821"/>
<source>&amp;Comment line(s)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2829"/>
<source>&amp;Ordered list</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2838"/>
<source>&amp;Unordered list</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2843"/>
<source>B&amp;lockquote</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="594"/>
<source>The file {} does not exist. Has it been moved or deleted?</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1415"/>
<source>Install {}{} to use spellcheck</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1457"/>
<source>{} has no installed dictionaries</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1478"/>
<source>{}{} is not installed</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="689"/>
<source>Save project?</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="689"/>
<source>Save changes to project "{}" before closing?</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="689"/>
<source>Your changes will be lost if you don't save them.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1671"/>
<source>PyQt / Qt versions 5.11 and 5.12 are known to cause a crash which might result in a loss of data.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1672"/>
<source>PyQt {} and Qt {} are in use.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/mainWindow.py" line="1678"/>
<source>Proceed with import at your own risk</source>
<translation type="unfinished"/>
</message>
2019-12-22 04:42:49 +13:00
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="862"/>
<source>Allow POV</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2852"/>
2019-12-22 04:42:49 +13:00
<source>Search</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/mainWindow.ui" line="2855"/>
2019-12-22 04:42:49 +13:00
<source>Ctrl+F</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/search.py" line="45"/>
<source>F3</source>
<translation type="unfinished">F3</translation>
</message>
<message>
<location filename="../manuskript/ui/search.py" line="46"/>
<source>Shift+F3</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/search.py" line="50"/>
<source>Situation</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/search.py" line="51"/>
<source>Status</source>
<translation type="unfinished">Стан</translation>
</message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2860"/>
<source>&amp;Technical Support</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2863"/>
<source>How to obtain technical support for Manuskript.</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2866"/>
<source>F1</source>
<translation type="unfinished">F1</translation>
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2871"/>
<source>&amp;Locate log file...</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2874"/>
<source>Locate log file</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2877"/>
<source>Locate the diagnostic log file used for this session.</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/ui/mainWindow.ui" line="2880"/>
<source>Shift+F1</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1193"/>
<source>Sorry!</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1193"/>
<source>This session is not being logged.</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1202"/>
<source>A log file is a Work in Progress!</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1202"/>
<source>The log file "{}" will continue to be written to until Manuskript is closed.</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1202"/>
<source>It will now be displayed in your file manager, but is of limited use until you close Manuskript.</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1218"/>
<source>Error!</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
<message>
<location filename="../manuskript/mainWindow.py" line="1218"/>
<source>An error was encountered while trying to show the log file below in your file manager.</source>
<translation type="unfinished"/>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
</message>
2019-12-22 04:42:49 +13:00
</context>
<context>
<name>Search</name>
<message>
<location filename="../manuskript/ui/search.py" line="40"/>
<source>No results found</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
</context>
<context>
<name>Settings</name>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="14"/>
<source>Settings</source>
<translation type="unfinished">Налаштування</translation>
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="24"/>
<source>General</source>
<translation type="unfinished">Загальне</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="526"/>
<source>Revisions</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="34"/>
<source>Views</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2891"/>
<source>Labels</source>
<translation type="unfinished">Позначки</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3023"/>
<source>Status</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3097"/>
<source>Fullscreen</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="82"/>
<source>General settings</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="98"/>
<source>Application settings</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="247"/>
<source>Loading</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="259"/>
<source>Automatically load last project on startup</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="278"/>
<source>Saving</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="292"/>
<source>Automatically save every</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="339"/>
<source>minutes.</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="375"/>
<source>If no changes during</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="422"/>
<source>seconds.</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="456"/>
<source>Save on project close</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="472"/>
<source>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p&gt;If you check this option, your project will be saved as one single file. Easier to copy or backup, but does not allow collaborative editing, or versioning.&lt;br/&gt;If this is unchecked, your project will be saved as a folder containing many small files.&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="478"/>
<source>Save to one single file</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="536"/>
<source>Revisions are a way to keep track of modifications. For each text item, it stores any changes you make to the main text, allowing you to see and restoring previous versions.</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="546"/>
<source>Keep revisions</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="562"/>
<source>S&amp;mart remove</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="577"/>
<source>Keep:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="590"/>
<source>Smart remove allows you to keep only a certain number of revisions. It is strongly recommended to use it, lest you file will becomes full of thousands of insignificant changes.</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="606"/>
<source>revisions per day for the last month</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="647"/>
<source>revisions per minute for the last 10 minutes</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="660"/>
<source>revisions per hour for the last day</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="673"/>
<source>revisions per 10 minutes for the last hour</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="798"/>
<source>revisions per week till the end of time</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="856"/>
<source>Views settings</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="874"/>
<source>Tree</source>
<translation type="unfinished">Дерево</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2145"/>
<source>Colors</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1889"/>
<source>Icon color:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2095"/>
<source>Nothing</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2100"/>
<source>POV</source>
<translation type="unfinished">З погляду</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2105"/>
<source>Label</source>
<translation type="unfinished">Позначка</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2110"/>
<source>Progress</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2115"/>
<source>Compile</source>
<translation type="unfinished">Експорт</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1937"/>
<source>Text color:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1985"/>
<source>Background color:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1168"/>
<source>Folders</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1180"/>
<source>Show ite&amp;m count</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1315"/>
<source>Show summary</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1245"/>
<source>&amp;Nothing</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1264"/>
<source>Text</source>
<translation type="unfinished">Текст</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1382"/>
<source>Outline</source>
<translation type="unfinished">Обрис</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1574"/>
<source>Visible columns</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1586"/>
<source>Goal</source>
<translation type="unfinished">Мета</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1602"/>
<source>Word count</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1618"/>
<source>Percentage</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1698"/>
<source>Title</source>
<translation type="unfinished">Назва</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1729"/>
<source>Index cards</source>
<translation type="unfinished">Каталог</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1874"/>
<source>Item colors</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2033"/>
<source>Border color:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2081"/>
<source>Corner color:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1741"/>
<source>Background</source>
<translation type="unfinished">Тло</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3576"/>
<source>Color:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2938"/>
<source>Ctrl+S</source>
<translation type="unfinished">Ctrl+S</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3318"/>
<source>Image:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2131"/>
<source>Text editor</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2250"/>
<source>Font</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2262"/>
<source>Family:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3619"/>
<source>Size:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3633"/>
<source>Misspelled:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2157"/>
<source>Background:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2473"/>
<source>Paragraphs</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3660"/>
<source>Line spacing:</source>
<translation type="unfinished">Міжрядковий інтервал:</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3668"/>
<source>Single</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3673"/>
<source>1.5 lines</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3678"/>
<source>Double</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3683"/>
<source>Proportional</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3700"/>
<source>%</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3716"/>
<source>Tab width:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3780"/>
<source> px</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3802"/>
<source>Indent 1st line</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3745"/>
<source>Spacing:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3144"/>
<source>New</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3158"/>
<source>Edit</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3168"/>
<source>Delete</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3212"/>
<source>Theme name:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3228"/>
<source>Apply</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3241"/>
<source>Cancel</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3271"/>
<source>Window Background</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3276"/>
<source>Text Background</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3281"/>
<source>Text Options</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3286"/>
<source>Paragraph Options</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3328"/>
<source>Type:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3336"/>
<source>No Image</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3341"/>
<source>Tiled</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3346"/>
<source>Centered</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3445"/>
<source>Stretched</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3356"/>
<source>Scaled</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3361"/>
<source>Zoomed</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3396"/>
<source>Opacity:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3422"/>
<source>Position:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3810"/>
<source>Left</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3819"/>
<source>Center</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3828"/>
<source>Right</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3453"/>
<source>Width:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3504"/>
<source>Corner radius:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3511"/>
<source>Margins:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3540"/>
<source>Padding:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3596"/>
<source>Font:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1833"/>
<source>Style</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2750"/>
<source>Cursor</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2762"/>
<source>Use block insertion of</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2485"/>
<source>Alignment:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3837"/>
<source>Justify</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="3849"/>
<source>Alignment</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1066"/>
<source>Icon Size</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1078"/>
<source>TextLabel</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2797"/>
<source>Disable blinking</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2364"/>
<source>Text area</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2376"/>
<source>Max width</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2408"/>
<source>Left/Right margins:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2437"/>
<source>Top/Bottom margins:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1219"/>
<source>S&amp;how progress</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1232"/>
<source>Show summar&amp;y</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1302"/>
<source>Show p&amp;rogress</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1845"/>
<source>Old st&amp;yle</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2189"/>
<source>Transparent</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2234"/>
<source>Restore defaults</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="138"/>
<source>Style:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="161"/>
<source>Language:</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="184"/>
<source>Font size:</source>
<translation type="unfinished">Розмір шрифту:</translation>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="112"/>
<source>Restarting Manuskript ensures all settings take effect.</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1193"/>
<source>Show &amp;word count</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1276"/>
<source>&amp;Show word count</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="1858"/>
<source>&amp;New style</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2810"/>
<source>Typewriter mode</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2823"/>
<source>Focus mode</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2837"/>
<source>None</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2842"/>
<source>Sentence</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2847"/>
<source>Line</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="2852"/>
<source>Paragraph</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/settings_ui.ui" line="821"/>
<source>&lt;p&gt;&lt;b&gt;The Revisions feature has been at the source of many reported issues. In this version of Manuskript it has been turned off by default for new projects in order to provide the best experience.&lt;/b&gt;&lt;/p&gt;&lt;p&gt;Why aren't these issues fixed already? &lt;a href="https://www.theologeek.ch/manuskript/contribute/"&gt;We need your help to make Manuskript better!&lt;/a&gt;&lt;/p&gt;</source>
<translation type="unfinished"/>
</message>
2019-12-22 04:42:49 +13:00
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="211"/>
<source>Show progress in chars next
to words</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="1113"/>
<source>Char/Word Counter</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="1137"/>
<source>Count spaces as chars</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="1206"/>
<source>Show char c&amp;ount</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/settings_ui.ui" line="1289"/>
<source>Sho&amp;w char count</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
</context>
<context>
<name>SpellAction</name>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="611"/>
<source>Spelling Suggestions</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="629"/>
<source>&amp;Add to dictionary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="682"/>
<source>&amp;Remove from custom dictionary</source>
<translation type="unfinished"/>
</message>
2019-12-22 04:42:49 +13:00
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="538"/>
2019-12-22 04:42:49 +13:00
<source>&amp;New Character</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="545"/>
2019-12-22 04:42:49 +13:00
<source>&amp;New Plot Item</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="552"/>
2019-12-22 04:42:49 +13:00
<source>&amp;New World Item</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="653"/>
2019-12-22 04:42:49 +13:00
<source>&amp;Correction Suggestions</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="662"/>
2019-12-22 04:42:49 +13:00
<source>&amp;Correction Suggestion</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
</context>
<context>
<name>about</name>
<message>
<location filename="../manuskript/ui/about_ui.ui" line="17"/>
<source>About Manuskript</source>
<translation type="unfinished">Про Манускрипт</translation>
</message>
<message>
<location filename="../manuskript/ui/about_ui.ui" line="50"/>
<source>Manuskript</source>
<translation type="unfinished">Манускрипт</translation>
</message>
</context>
<context>
<name>aboutDialog</name>
<message>
<location filename="../manuskript/ui/about.py" line="28"/>
<source>Version</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/about.py" line="41"/>
<source>Software Versions in Use:</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>abstractModel</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="199"/>
<source>Title</source>
<translation type="unfinished">Назва</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="201"/>
<source>POV</source>
<translation type="unfinished">З погляду</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="203"/>
<source>Label</source>
<translation type="unfinished">Позначка</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="205"/>
<source>Status</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="207"/>
<source>Compile</source>
<translation type="unfinished">Експорт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="209"/>
<source>Word count</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/abstractModel.py" line="211"/>
<source>Goal</source>
<translation type="unfinished">Мета</translation>
</message>
</context>
<context>
<name>basicItemView</name>
<message>
<location filename="../manuskript/ui/views/basicItemView_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/basicItemView_ui.ui" line="38"/>
<source>POV:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/basicItemView_ui.ui" line="55"/>
<source>Goal:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/basicItemView_ui.ui" line="80"/>
<source>Word count</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/basicItemView_ui.ui" line="92"/>
<source>One line summary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/basicItemView_ui.ui" line="99"/>
<source>Few sentences summary:</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>characterModel</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/characterModel.py" line="205"/>
<source>Name</source>
<translation type="unfinished">Ім'я</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/characterModel.py" line="207"/>
<source>Value</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>characterTreeView</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/characterTreeView.py" line="32"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/characterTreeView.py" line="32"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/characterTreeView.py" line="32"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>cheatSheet</name>
<message>
<location filename="../manuskript/ui/cheatSheet_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet_ui.ui" line="46"/>
<source>Filter (type the name of anything in your project)</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="113"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="113"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="113"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="91"/>
<source>Characters</source>
<translation type="unfinished">Персонажі</translation>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="104"/>
<source>Texts</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="116"/>
<source>Plots</source>
<translation type="unfinished">Сюжети</translation>
</message>
<message>
<location filename="../manuskript/ui/cheatSheet.py" line="120"/>
<source>World</source>
<translation type="unfinished">Світ</translation>
</message>
</context>
<context>
<name>cmbOutlineCharacterChoser</name>
<message>
<location filename="../manuskript/ui/views/cmbOutlineCharacterChoser.py" line="34"/>
<source>None</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/cmbOutlineCharacterChoser.py" line="36"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/cmbOutlineCharacterChoser.py" line="36"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/cmbOutlineCharacterChoser.py" line="36"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/cmbOutlineCharacterChoser.py" line="136"/>
<source>Various</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>cmbOutlineLabelChoser</name>
<message>
<location filename="../manuskript/ui/views/cmbOutlineLabelChoser.py" line="113"/>
<source>Various</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>cmbOutlineStatusChoser</name>
<message>
<location filename="../manuskript/ui/views/cmbOutlineStatusChoser.py" line="112"/>
<source>Various</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>collapsibleDockWidgets</name>
<message>
<location filename="../manuskript/ui/collapsibleDockWidgets.py" line="26"/>
<source>Dock Widgets Toolbar</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>completer</name>
<message>
<location filename="../manuskript/ui/editors/completer_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>corkDelegate</name>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/views/corkDelegate.py" line="70"/>
<source>One line summary</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/ui/views/corkDelegate.py" line="100"/>
<source>Full summary</source>
<translation type="unfinished">Загальний опис</translation>
</message>
</context>
<context>
<name>editorWidget_ui</name>
<message>
<location filename="../manuskript/ui/editors/editorWidget_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>exporter</name>
<message>
<location filename="../manuskript/ui/exporters/exporter_ui.ui" line="65"/>
<source>Export</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exporter_ui.ui" line="22"/>
<source>Export to:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exporter_ui.ui" line="32"/>
<source>Manage exporters</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exporter_ui.ui" line="103"/>
<source>Preview</source>
<translation type="unfinished">Попередній перегляд</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/exporter_ui.ui" line="81"/>
<source>Settings</source>
<translation type="unfinished">Налаштування</translation>
</message>
</context>
<context>
<name>exporterDialog</name>
<message>
<location filename="../manuskript/ui/exporters/exporter.py" line="64"/>
<source>{} (not implemented yet)</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>exporterSettings</name>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="50"/>
<source>Content</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="56"/>
<source>Decide here what will be included in the final export.</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="85"/>
<source>Type</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="90"/>
<source>Title</source>
<translation type="unfinished">Назва</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings.py" line="326"/>
<source>Text</source>
<translation type="unfinished">Текст</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="118"/>
<source>I need more granularity</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="127"/>
<source>Fi&amp;lters</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="142"/>
<source>&lt;html&gt;&lt;head/&gt;&lt;body&gt;&lt;p&gt;Filters what items will be included in the final export.&lt;br/&gt;&lt;span style=" color:#773333;"&gt;(Not fully implemented yet.)&lt;/span&gt;&lt;/p&gt;&lt;/body&gt;&lt;/html&gt;</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="149"/>
<source>Ignore compile status (include all items)</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="156"/>
<source>Subitems of:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="170"/>
<source>Labels</source>
<translation type="unfinished">Позначки</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="177"/>
<source>Status</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="229"/>
<source>Separations</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="241"/>
<source>Between folders:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings.py" line="86"/>
<source>Empty line</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings.py" line="105"/>
<source>Custom</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="367"/>
<source>Between texts:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="493"/>
<source>Between folder and text:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="619"/>
<source>Between text and folder:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="764"/>
<source>Transformations</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="773"/>
<source>Typographic replacements:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="802"/>
<source>Replace double quotes (") with:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="911"/>
<source>Replace single quotes (') with:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1020"/>
<source>Remove multiple spaces</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1030"/>
<source>Custom replacements:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1049"/>
<source>Enabled</source>
<translation>Увімкнено</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1054"/>
<source>Replace</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1059"/>
<source>With</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1064"/>
<source>RegExp</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1067"/>
<source>If checked, uses regular expression for replacement. If unchecked, replaced as plain text.</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1151"/>
<source>Preview</source>
<translation>Попередній перегляд</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1157"/>
<source>Font</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1163"/>
<source>Font:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="1173"/>
<source>Font size:</source>
<translation type="unfinished">Розмір шрифту:</translation>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings.py" line="320"/>
<source>Folder</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings.py" line="343"/>
<source>{}Level {} folder</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings.py" line="346"/>
<source>{}Level {} text</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="788"/>
<source>Replace ... with </source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/manuskript/plainTextSettings_ui.ui" line="795"/>
<source>Replace --- with </source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>exportersManager</name>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="81"/>
<source>Installed</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="87"/>
<source>Custom</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="93"/>
<source>Not found</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="96"/>
<source>{} not found. Install it, or set path manually.</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="124"/>
<source>&lt;b&gt;Status:&lt;/b&gt; uninstalled.</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="126"/>
<source>&lt;b&gt;Requires:&lt;/b&gt; </source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/exporters/exportersManager.py" line="133"/>
<source>Set {} executable path.</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>frequencyAnalyzer</name>
<message>
<location filename="../manuskript/ui/tools/frequencyAnalyzer.py" line="70"/>
<source>Phrases</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/tools/frequencyAnalyzer.py" line="108"/>
<source>Frequency</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/tools/frequencyAnalyzer.py" line="108"/>
<source>Word</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>fullScreenEditor</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="133"/>
<source>Theme:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="364"/>
<source>{} words / {}</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="368"/>
<source>{} words</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="153"/>
<source>Spellcheck</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="154"/>
<source>Navigation</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="155"/>
<source>New Text</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="156"/>
<source>Title</source>
<translation type="unfinished">Назва</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="157"/>
<source>Title: Show Full Path</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="159"/>
<source>Theme selector</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="160"/>
<source>Word count</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="161"/>
<source>Progress</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="162"/>
<source>Progress: Auto Show/Hide</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="163"/>
<source>Clock</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="164"/>
<source>Clock: Show Seconds</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>generalSettings</name>
<message>
<location filename="../manuskript/ui/importers/generalSettings_ui.ui" line="41"/>
<source>General</source>
<translation type="unfinished">Загальне</translation>
</message>
<message>
<location filename="../manuskript/ui/importers/generalSettings_ui.ui" line="55"/>
<source>Split scenes at:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/generalSettings_ui.ui" line="65"/>
<source>\n---\n</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/generalSettings_ui.ui" line="72"/>
<source>Trim long titles (&gt; 32 chars)</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/generalSettings_ui.ui" line="86"/>
<source>Import under:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/generalSettings_ui.ui" line="93"/>
<source>Import in a top-level folder</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>helpLabel</name>
<message>
<location filename="../manuskript/ui/helpLabel.py" line="12"/>
<source>If you don't wanna see me, you can hide me in Help menu.</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>importer</name>
<message>
<location filename="../manuskript/ui/importers/importer_ui.ui" line="119"/>
<source>Import</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/importer_ui.ui" line="22"/>
<source>Format:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/importer_ui.ui" line="45"/>
<source>Choose file</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/importer_ui.ui" line="75"/>
<source>Clear file</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/importers/importer_ui.ui" line="160"/>
<source>Preview</source>
<translation type="unfinished">Попередній перегляд</translation>
</message>
<message>
<location filename="../manuskript/ui/importers/importer_ui.ui" line="138"/>
<source>Settings</source>
<translation type="unfinished">Налаштування</translation>
</message>
</context>
<context>
<name>lineEditView</name>
<message>
<location filename="../manuskript/ui/views/lineEditView.py" line="114"/>
<source>Various</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>locker</name>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="26"/>
<source>Lock screen:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="33"/>
<source>Word target</source>
<translation>Бажана кількість слів</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="40"/>
<source>Time target</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="47"/>
<source> words</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="63"/>
<source> minutes</source>
<translation> хвилин</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/locker_ui.ui" line="79"/>
<source>Lock !</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker.py" line="94"/>
<source>~{} h.</source>
<translation>~{} г.</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/locker.py" line="96"/>
<source>~{} mn.</source>
<translation>~{} хв.</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/locker.py" line="100"/>
<source>{}:{}</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker.py" line="102"/>
<source>{} s.</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker.py" line="104"/>
<source>{} remaining</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/locker.py" line="109"/>
<source>{} words remaining</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>mainEditor</name>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="67"/>
<source>Text</source>
<translation type="unfinished">Текст</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="83"/>
<source>Index cards</source>
<translation type="unfinished">Каталог</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="102"/>
<source>Outline</source>
<translation type="unfinished">Обрис</translation>
</message>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="198"/>
<source>F11</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="47"/>
<source>Go to parent item</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/mainEditor_ui.ui" line="57"/>
<source>Alt+Up</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/mainEditor.py" line="251"/>
<source>Root</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/mainEditor.py" line="358"/>
2019-12-22 04:42:49 +13:00
<source>{} words </source>
<translation>{} слів </translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/mainEditor.py" line="339"/>
2019-12-22 04:42:49 +13:00
<source>({} chars) {} words / {} </source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/mainEditor.py" line="345"/>
2019-12-22 04:42:49 +13:00
<source>{} words / {} </source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/mainEditor.py" line="360"/>
2019-12-22 04:42:49 +13:00
<source>{} chars</source>
<translation type="unfinished"/>
2019-12-22 04:42:49 +13:00
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/mainEditor.py" line="354"/>
2019-12-22 04:42:49 +13:00
<source>{} chars </source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>markdownSettings</name>
<message>
<location filename="../manuskript/exporter/manuskript/markdown.py" line="58"/>
<source>Markdown</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>metadataView</name>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="41"/>
<source>Properties</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="81"/>
<source>Summary</source>
<translation type="unfinished">Стислий переказ</translation>
</message>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="114"/>
<source>One line summary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="140"/>
<source>Full summary</source>
<translation type="unfinished">Загальний опис</translation>
</message>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="180"/>
<source>Notes / References</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/metadataView_ui.ui" line="190"/>
<source>Revisions</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>myPanel</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/fullScreenEditor.py" line="599"/>
<source>Auto-hide</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>outlineBasics</name>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="134"/>
<source>Set POV</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="136"/>
<source>None</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="163"/>
<source>Set Status</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="179"/>
<source>Set Label</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="283"/>
<source>New</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="142"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="143"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="144"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="197"/>
<source>Set Custom Icon</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="198"/>
<source>Restore to default</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="61"/>
<source>Root</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="75"/>
<source>Open {} items in new tabs</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="78"/>
<source>Open {} in a new tab</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="328"/>
<source>About to remove</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="434"/>
<source>Select at least two items. Folders are ignored.</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="443"/>
<source>All items must be on the same level (share the same parent).</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="88"/>
<source>New &amp;Folder</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="94"/>
<source>New &amp;Text</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="108"/>
<source>&amp;Copy</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="103"/>
<source>C&amp;ut</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="113"/>
<source>&amp;Paste</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="125"/>
<source>&amp;Rename</source>
<translation type="unfinished">&amp;Перейменувати</translation>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="119"/>
<source>&amp;Delete</source>
<translation type="unfinished">&amp;Вилучити</translation>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="315"/>
<source>You're about to delete {} item(s).</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineBasics.py" line="325"/>
<source>Are you sure?</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>outlineCharacterDelegate</name>
<message>
<location filename="../manuskript/ui/views/outlineDelegates.py" line="141"/>
<source>None</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineDelegates.py" line="143"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineDelegates.py" line="143"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/outlineDelegates.py" line="143"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>outlineItem</name>
<message>
<location filename="../manuskript/models/outlineItem.py" line="256"/>
<source>{} words / {} ({})</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/outlineItem.py" line="261"/>
<source>{} words</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>pandocSettings</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="166"/>
<source>General</source>
<translation type="unfinished">Загальне</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="180"/>
<source>Table of Content</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/exporter/pandoc/abstractPlainText.py" line="185"/>
<source>Custom settings for {}</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>persosProxyModel</name>
<message>
<location filename="../manuskript/models/persosProxyModel.py" line="16"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/persosProxyModel.py" line="17"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/persosProxyModel.py" line="18"/>
<source>Minors</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>plotDelegate</name>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>General</source>
<translation type="unfinished">Загальне</translation>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Promise</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Problem</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Progress</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Resolution</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Try / Fail</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>No and</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Yes but</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Freytag's pyramid</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Exposition</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Rising action</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Climax</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Falling action</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Three acts</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>1. Setup</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>1. Inciting event</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>1. Turning point</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>2. Choice</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>2. Reversal</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>2. Disaster</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>3. Stand up</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>3. Climax</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>3. Ending</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Hero's journey</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Ordinary world</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Call to adventure</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Refusal of the call</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Meeting with mentor</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Tests</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Approach</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Abyss</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Reward / Revelation</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Transformation</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Atonement</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/plotDelegate.py" line="33"/>
<source>Return</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>plotModel</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/plotModel.py" line="144"/>
<source>Name</source>
<translation type="unfinished">Ім'я</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/plotModel.py" line="146"/>
<source>Meta</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/plotModel.py" line="179"/>
<source>New step</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/plotModel.py" line="249"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/plotModel.py" line="249"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/plotModel.py" line="249"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>plotTreeView</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/plotTreeView.py" line="127"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/plotTreeView.py" line="127"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/plotTreeView.py" line="127"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/views/plotTreeView.py" line="187"/>
<source>**Plot:** {}</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>plotsProxyModel</name>
<message>
<location filename="../manuskript/models/plotsProxyModel.py" line="22"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/plotsProxyModel.py" line="23"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/plotsProxyModel.py" line="24"/>
<source>Minors</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>propertiesView</name>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="195"/>
<source>POV</source>
<translation type="unfinished">З погляду</translation>
</message>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="215"/>
<source>Status</source>
<translation type="unfinished">Стан</translation>
</message>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="235"/>
<source>Label</source>
<translation type="unfinished">Позначка</translation>
</message>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="255"/>
<source>Compile</source>
<translation type="unfinished">Експорт</translation>
</message>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="269"/>
<source>Goal</source>
<translation type="unfinished">Мета</translation>
</message>
<message>
<location filename="../manuskript/ui/views/propertiesView_ui.ui" line="291"/>
<source>Word count</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>references</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="501"/>
<source>Not a reference: {}.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="399"/>
<source>Unknown reference: {}.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="106"/>
<source>Path:</source>
<translation type="unfinished">Шлях:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="107"/>
<source>Stats:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="108"/>
<source>POV:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="109"/>
<source>Status:</source>
<translation type="unfinished">Стан:</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="110"/>
<source>Label:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="111"/>
<source>Short summary:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="112"/>
<source>Long summary:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="113"/>
<source>Notes:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/references.py" line="201"/>
<source>Basic info</source>
<translation type="unfinished">Загальна інформація</translation>
</message>
<message>
<location filename="../manuskript/models/references.py" line="202"/>
<source>Detailed info</source>
<translation type="unfinished">Докладна інформація</translation>
</message>
<message>
<location filename="../manuskript/models/references.py" line="203"/>
<source>POV of:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="364"/>
<source>Go to {}.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="359"/>
<source>Description</source>
<translation type="unfinished">Опис</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="281"/>
<source>Result</source>
<translation type="unfinished">Результат</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="282"/>
<source>Characters</source>
<translation type="unfinished">Персонажі</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="283"/>
<source>Resolution steps</source>
<translation type="unfinished">Кроки розвитку сюжету</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="360"/>
<source>Passion</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="361"/>
<source>Conflict</source>
<translation type="unfinished">Конфлікт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="498"/>
<source>&lt;b&gt;Unknown reference:&lt;/b&gt; {}.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="506"/>
<source>Folder: &lt;b&gt;{}&lt;/b&gt;</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="508"/>
<source>Text: &lt;b&gt;{}&lt;/b&gt;</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="513"/>
<source>Character: &lt;b&gt;{}&lt;/b&gt;</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="516"/>
<source>Plot: &lt;b&gt;{}&lt;/b&gt;</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="519"/>
<source>World: &lt;b&gt;{name}&lt;/b&gt;{path}</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/models/references.py" line="592"/>
<source>Referenced in:</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/references.py" line="212"/>
<source>Motivation</source>
<translation type="unfinished">Мотивація</translation>
</message>
<message>
<location filename="../manuskript/models/references.py" line="213"/>
<source>Goal</source>
<translation type="unfinished">Мета</translation>
</message>
<message>
<location filename="../manuskript/models/references.py" line="215"/>
<source>Epiphany</source>
<translation type="unfinished">Прояснення</translation>
</message>
<message>
<location filename="../manuskript/models/references.py" line="216"/>
<source>Short summary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/models/references.py" line="217"/>
<source>Longer summary</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>revisions</name>
<message>
<location filename="../manuskript/ui/revisions_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions_ui.ui" line="107"/>
<source>Options</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/revisions.py" line="257"/>
<source>Restore</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/revisions.py" line="258"/>
<source>Delete</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="45"/>
<source>Show modifications</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="52"/>
<source>Show ancient version</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="60"/>
<source>Show spaces</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="66"/>
<source>Show modifications only</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="110"/>
<source>{} years ago</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="112"/>
<source>{} months ago</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="114"/>
<source>{} days ago</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="116"/>
<source>1 day ago</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="118"/>
<source>{} hours ago</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="120"/>
<source>{} minutes ago</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/revisions.py" line="122"/>
<source>{} seconds ago</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/revisions.py" line="182"/>
<source>Line {}:</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/revisions.py" line="261"/>
<source>Clear all</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>search</name>
<message>
<location filename="../manuskript/ui/search_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/search_ui.ui" line="46"/>
<source>Search for...</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>settingsWindow</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="674"/>
<source>New status</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="695"/>
<source>New label</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="731"/>
<source>newtheme</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="741"/>
<source>New theme</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="773"/>
<source> (read-only)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="534"/>
<source>Open Image</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="534"/>
<source>Image files (*.jpg; *.jpeg; *.png)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="550"/>
<source>Error</source>
<translation type="unfinished">Помилка</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="547"/>
<source>Unable to load selected file</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/settingsWindow.py" line="550"/>
<source>Unable to add selected image:
{}</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>sldImportance</name>
<message>
<location filename="../manuskript/ui/views/sldImportance_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/sldImportance_ui.ui" line="39"/>
<source>TextLabel</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/sldImportance.py" line="29"/>
<source>Minor</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/sldImportance.py" line="30"/>
<source>Secondary</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/sldImportance.py" line="31"/>
<source>Main</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>splitDialog</name>
<message>
<location filename="../manuskript/ui/tools/splitDialog.py" line="19"/>
<source>
&lt;p&gt;Split selected item(s) at the given mark.&lt;/p&gt;
&lt;p&gt;If one of the selected item is a folder, it will be applied
recursively to &lt;i&gt;all&lt;/i&gt; of it's children items.&lt;/p&gt;
&lt;p&gt;The split mark can contain following escape sequences:
&lt;ul&gt;
&lt;li&gt;&lt;b&gt;&lt;code&gt;\n&lt;/code&gt;&lt;/b&gt;: line break&lt;/li&gt;
&lt;li&gt;&lt;b&gt;&lt;code&gt;\t&lt;/code&gt;&lt;/b&gt;: tab&lt;/li&gt;
&lt;/ul&gt;
&lt;/p&gt;
&lt;p&gt;&lt;b&gt;Mark:&lt;/b&gt;&lt;/p&gt;
</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/tools/splitDialog.py" line="47"/>
<source>Split '{}'</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/tools/splitDialog.py" line="51"/>
<source>Split items</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>storylineView</name>
<message>
<location filename="../manuskript/ui/views/storylineView_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/storylineView.py" line="36"/>
<source>Show Plots</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/storylineView.py" line="43"/>
<source>Show Characters</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>tabSplitter</name>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/tabSplitter.py" line="67"/>
<source>Open selected items in that view.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/tabSplitter.py" line="158"/>
<source>Split horizontally</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/tabSplitter.py" line="168"/>
<source>Close split</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/editors/tabSplitter.py" line="204"/>
<source>Split vertically</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>textEditView</name>
<message>
<location filename="../manuskript/ui/views/textEditView.py" line="324"/>
<source>Various</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>textFormat</name>
<message>
<location filename="../manuskript/ui/editors/textFormat_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="18"/>
<source>CTRL+B</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="19"/>
<source>CTRL+I</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="20"/>
<source>CTRL+U</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="21"/>
<source>CTRL+P</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="22"/>
<source>CTRL+L</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="23"/>
<source>CTRL+E</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="24"/>
<source>CTRL+R</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/editors/textFormat.py" line="25"/>
<source>CTRL+J</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>treeView</name>
<message>
<location filename="../manuskript/ui/views/treeView.py" line="48"/>
<source>Expand {}</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/treeView.py" line="52"/>
<source>Collapse {}</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/treeView.py" line="59"/>
<source>Expand All</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/views/treeView.py" line="63"/>
<source>Collapse All</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>welcome</name>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="14"/>
<source>Form</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="50"/>
<source>1</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="55"/>
<source>Templates</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="86"/>
<source>Empty</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="225"/>
<source>Novel</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="230"/>
<source>Novella</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="235"/>
<source>Short Story</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="247"/>
<source>Research paper</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="418"/>
<source>Demo projects</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="177"/>
<source>Add level</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="190"/>
<source>Add word count</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="213"/>
<source>Next time, automatically open last project</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="238"/>
<source>Open...</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="248"/>
<source>Recent</source>
<translation type="unfinished"/>
</message>
<message>
<location filename="../manuskript/ui/welcome_ui.ui" line="258"/>
<source>Create</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="158"/>
<source>Open project</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="158"/>
<source>Manuskript project (*.msk);;All files (*)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="172"/>
<source>Save project as...</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="196"/>
<source>Manuskript project (*.msk)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="188"/>
<source>Manuskript</source>
<translation type="unfinished">Манускрипт</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="196"/>
<source>Create New Project</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="208"/>
<source>Warning</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="208"/>
<source>Overwrite existing project {} ?</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="224"/>
<source>Empty fiction</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="448"/>
<source>Chapter</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="449"/>
<source>Scene</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="239"/>
<source>Trilogy</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="239"/>
<source>Book</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="247"/>
<source>Section</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="246"/>
<source>Empty non-fiction</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="308"/>
<source>words each.</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="311"/>
<source>of</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="335"/>
<source>Text</source>
<translation type="unfinished">Текст</translation>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="338"/>
<source>Something</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="384"/>
<source>&lt;b&gt;Total:&lt;/b&gt; {} words (~ {} pages)</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="405"/>
<source>Fiction</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="411"/>
<source>Non-fiction</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="446"/>
<source>Idea</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="447"/>
<source>Note</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="450"/>
<source>Research</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="457"/>
<source>TODO</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="458"/>
<source>First draft</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="459"/>
<source>Second draft</source>
<translation type="unfinished"/>
</message>
<message>
Friendly logging for end users (#859) * Changed default logging behaviour We now log by default to a timestamped file in $datadir/logs/. No longer shall restarting Manuskript after a crash wipe a very useful logfile. Logs older than 35 days in the $datadir/logs/ directory are pruned during startup. In case of subtle corruption detected a few weeks after the fact, relevant logs might still exist to explain what had happened... yet it does not come at the cost of infinitely gobbling up a users storage space, either. The --logfile (-L) argument can now utilize strftime() specifiers. A special modifier %# is also supported which will insert the process id. Besides being an added factor of uniqueness for a filename, it can also be relevant to help identify the log file belonging to a misbehaving Manuskript process. * Added support-related items to Help menu The 'Technical Support' item should lead to a landing page that will guide the user to the most efficient way to resolve their problem. How to report bugs and submit logs would be one of those. The 'Locate Log File' item should open a file manager window with the logfile of this session highlighted. Because Manuskript is still writing to it, we first remind them of its limited use until Manuskript is closed. This approach was chosen because users might want to locate the file prior to reproducing a bug, or because they'd like to look at other logs from previous sessions. * Updated translation files and added german translation Co-authored-by: TheJackiMonster <thejackimonster@gmail.com>
2021-04-13 23:32:46 +12:00
<location filename="../manuskript/ui/welcome.py" line="460"/>
<source>Final</source>
<translation type="unfinished"/>
</message>
</context>
<context>
<name>worldModel</name>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="136"/>
<source>New item</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Fantasy world building</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Physical</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Climate</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Topography</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Astronomy</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Wild life</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Flora</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>History</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Races</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Diseases</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Cultural</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Customs</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Food</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Languages</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Education</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Dresses</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Science</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Calendar</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Bodily language</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Ethics</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Religion</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Government</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Politics</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Gender roles</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Music and arts</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Architecture</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Military</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Technology</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Courtship</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Demography</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Transportation</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="262"/>
<source>Medicine</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="285"/>
<source>Magic system</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="285"/>
<source>Rules</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="285"/>
<source>Organization</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="285"/>
<source>Magical objects</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="285"/>
<source>Magical places</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="285"/>
<source>Magical races</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="292"/>
<source>Important places</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="293"/>
<source>Important objects</source>
<translation type="unfinished"/>
</message>
<message>
2019-12-22 04:42:49 +13:00
<location filename="../manuskript/models/worldModel.py" line="251"/>
<source>Natural resources</source>
<translation type="unfinished"/>
</message>
</context>
</TS>