Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2024-07-12 23:55:07 +00:00
Code Issues Packages Projects Releases Wiki Activity
reactos/base/setup/usetup/lang/de-DE.h

2341 lines
50 KiB
C
Raw Normal View History

[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
// This file is converted by code7bit.
// code7bit: https://github.com/katahiromz/code7bit
// To revert conversion, please execute "code7bit -r <file>".
- Move from using include guards to pragma once. - Whilst this is non-standard and potentially makes the code less portable, it's supported by both gcc and msvc and should bringg increased compilation speed due to its optimized behaviour (doesn't need to invoke the preprocessor) - Patch by Amine Khaldi [amine.khaldi@reactos.org] svn path=/trunk/; revision=45685
2010-02-26 11:43:19 +00:00
#pragma once
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
static MUI_ENTRY deDESetupInitPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
},
{
0,
20,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Bitte warten Sie w\204hrend das ReactOS Setup startet",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER,
TEXT_ID_STATIC
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
},
{
0,
21,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"und Ihre Ger\204te detektiert...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER,
TEXT_ID_STATIC
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
},
{
0,
0,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Bitte warten...",
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_ID_STATIC
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
},
{
0,
0,
NULL,
0
}
};
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
static MUI_ENTRY deDELanguagePageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
{
6,
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Sprachauswahl",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
},
{
8,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Bitte w\204hlen Sie die Sprache, die Sie w\204hrend der Installation",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
},
{
[USETUP] Fix a little layout issue. svn path=/trunk/; revision=56817
2012-07-01 15:55:14 +00:00
11,
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"verwenden wollen. Best\204tigen Sie die Auswahl mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
},
{
8,
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Diese Sprache wird sp\204ter als Standardsprache im System verwendet.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEWelcomePageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
6,
8,
Giant German Language Fix Patch by "tux." I skipped xcopy, winhlp32 and wordpad because they are wine synched and expand, because its not translated anymore. Fix some BOMs i did not see at wine synching. svn path=/trunk/; revision=45501
2010-02-08 19:35:26 +00:00
"Willkommen zum ReactOS-Setup",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
6,
11,
Giant German Language Fix Patch by "tux." I skipped xcopy, winhlp32 and wordpad because they are wine synched and expand, because its not translated anymore. Fix some BOMs i did not see at wine synching. svn path=/trunk/; revision=45501
2010-02-08 19:35:26 +00:00
"Dieser Teil des Setups kopiert das ReactOS-Betriebssystem auf Ihren",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
6,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Computer und bereitet die n\204chsten Schritte vor.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
15,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"\x07 Dr\201cken Sie ENTER, um ReactOS zu installieren / aktualisieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
17,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie R, um ReactOS zu reparieren. (Wiederherstellungskonsole)",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
19,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie L, um das Lizenzabkommen von ReactOS zu lesen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie F3, um die Installation abzubrechen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
23,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Weitere Informationen erhalten Sie unter:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
24,
[USETUP] Update now-redirected 'http' and 'www.reactos.org' URLs (#2622) NB: http://www.reactos.org/uk/ is not updated, as it returns Error 404 - Page not found.
2020-04-22 05:44:13 +00:00
"https://reactos.org/",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen R = Reparieren L = Lizenz F3 = Beenden",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEIntroPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
4,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
8,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
"ReactOS Version Status",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
11,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"ReactOS befindet sich noch im Alpha Stadium. Noch sind nicht alle",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
12,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"wichtigen Funktionen implementiert und Sie m\201ssen mit dem Auftreten",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
13,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"schwerwiegender Fehler rechnen. Verwenden Sie es daher nur",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
6,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
14,
"zu Testzwecken auf einem Zweitcomputer, nicht als Produktivsystem!",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
},
{
6,
16,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Sichern Sie unbedingt vorher ihre bestehenden Daten!",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
19,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"\x07 Dr\201cken Sie ENTER, um das ReactOS Setup fortzusetzen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
21,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie F3, um abzubrechen ohne ReactOS zu installieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen F3 = Abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDELicensePageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
6,
6,
"Lizenz:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"ReactOS ist unter den Bedingungen der GNU General Public License",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
9,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"lizenziert. Einige Teile von ReactOS stehen unter dazu kompatiblen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
10,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Lizenzen wie der BSD- oder GNU LGPL-Lizenz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Alle Softwarebestandteile in ReactOS sind daher unter der",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"GNU GPL ver\224ffentlicht, behalten daneben aber ihre",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"urspr\201nglichen Lizenzen bei.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
15,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS ist freie Software. Die Ver\224ffentlichung dieses Programms",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
16,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"erfolgt in der Hoffnung, dass es Ihnen von Nutzen sein wird,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
17,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"aber OHNE IRGENDEINE GARANTIE,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
18,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"sogar ohne die implizite Garantie der MARKTREIFE",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"oder der VERWENDBARKEIT F\232R EINEN BESTIMMTEN ZWECK.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
20,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Details finden Sie in der GNU General Public License.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
22,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Sie sollten ein Exemplar der GNU General Public License",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
23,
"zusammen mit ReactOS erhalten haben.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
24,
"Falls nicht, besuchen Sie bitte",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
26,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"http://www.gnu.org/licenses",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Zur\201ck",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
{
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEDevicePageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Die untere Liste zeigt die derzeitigen Ger\204teeinstellungen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
24,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
11,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Computertyp:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
24,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
12,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Anzeige:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
24,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
13,
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
"Tastatur:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
24,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
14,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Tastaturlayout:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
/*{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
24,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
16,
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
"Akzeptieren:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
},*/
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
25,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
16, "Diese Ger\204teeinstellungen akzeptieren",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
6,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie k\224nnen die Einstellungen durch die PFEILTASTEN ausw\204hlen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
20,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Dr\201cken Sie ENTER, um eine Einstellung zu \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
21,
" ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
23,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Wenn alle Einstellungen korrekt sind, w\204hlen Sie \"Diese Ger\204te-",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
24,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"einstellungen akzeptieren\" und best\204tigen mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDERepairPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Der Installationsassistent ist noch der Entwicklungsphase.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Er unterst\201tzt noch nicht alle Funktionen eines vollst\204ndig",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
6,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
12,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"nutzbaren Setups.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
},
[USETUP] Add the create logical partition page. svn path=/trunk/; revision=63574
2014-06-09 01:49:24 +00:00
{
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
6,
14,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
"Die Reparaturfunktionen sind noch nicht implementiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie U, um ReactOS zu aktualisieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie R, f\201r die Wiederherstellungskonsole.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
20,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie ESC, um zur Hauptseite zur\201ckzukehren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
22,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"\x07 Dr\201cken Sie ENTER, um den Computer neu zu starten.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
0,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ESC = Zur\201ck U = Aktualisieren R = Wiederherst. ENTER = Neustart",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
static MUI_ENTRY deDEUpgradePageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
8,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Das ReactOS Setup kann eine der unten aufgef\201hrten Installationen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
9,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"aktualisieren, oder versuchen,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
10,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"eine bestehende ReactOS Installation zu reparieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
12,
[USETUP] de-DE Fix typo CORE-16792 Fix typo in my last changeset 0.4.14-dev-1323-g d079342e0a0684b4fb6530ee7ea4728f2a0ae985
2020-04-06 18:55:18 +00:00
"Die Reparaturfunktionen sind noch nicht alle implementiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
15,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"\x07 W\204hlen Sie mit den PFEILTASTEN die gew\201nschte Installation aus.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
17,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie U, um die gew\204hlte Installation zu aktualisieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
19,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie ESC, um eine Neuinstallation vorzunehmen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
21,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie F3, um abzubrechen ohne ReactOS zu installieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
0,
0,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"U = Aktualisieren ESC = Neuinstallation F3 = Abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEComputerPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
6,
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Den zu installierenden Computertyp einstellen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie die PFEILTASTEN, um den gew\201nschten",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
eeevil trailing spaces :D svn path=/trunk/; revision=31249
2007-12-15 16:30:15 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
8,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" Typ zu w\204hlen. Best\204tigen Sie mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie ESC, um zur vorherigen Seite zur\201ckzukehren,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ohne den Computertyp zu \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Zur\201ck F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEFlushPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
10,
6,
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
"Die geschrieben Daten werden \201berpr\201ft.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
10,
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Dies kann einige Zeit in Anspruch nehmen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
10,
9,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Der PC startet automatisch neu, sobald der Vorgang beendet ist.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Der Zwischenspeicher wird geleert",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEQuitPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
10,
6,
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
"ReactOS wurde nicht vollst\204ndig installiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
10,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Entfernen Sie alle Datentr\204ger aus den CD-Laufwerken.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
10,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Dr\201cken Sie ENTER, um den Computer neu zu starten.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
"Bitte warten...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDEDisplayPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie wollen den zu installierenden Bildschirmtyp \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
{
8,
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Benutzen Sie die PFEILTASTEN, um den gew\201nschten",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" Typ zu w\204hlen. Best\204tigen Sie mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie ESC, um zur vorherigen Seite zur\201ckzukehren, ohne",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
8,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" den Bildschirmtyp zu \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Zur\201ck F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
static MUI_ENTRY deDESuccessPageEntries[] =
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
10,
6,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Grundkomponenten von ReactOS wurden erfolgreich installiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
10,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Entfernen Sie alle Datentr\204ger aus den CD-Laufwerken.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
10,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Dr\201cken Sie ENTER, um den Computer neu zu starten.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
0,
0,
NULL,
0
}
};
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
static MUI_ENTRY deDESelectPartitionEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Diese Liste zeigt die existierenden Partitionen und ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
6,
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"freien Speicherplatz f\201r neue Partitionen auf der Festplatte an.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
11,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Benutzen Sie die PFEILTASTEN, um eine Partition auszuw\204hlen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
13,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"\x07 ENTER best\204tigt Ihre Auswahl.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
15,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
"\x07 C erstellt eine prim\204re/logische Partition.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
17,
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"\x07 E erstellt eine erweiterte Partition.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
},
{
8,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 D l\224scht eine vorhandene Partition.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
"Bitte warten...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
static MUI_ENTRY deDEChangeSystemPartition[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
8,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Die derzeitige aktive Partition",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
12,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"auf dem Systemlaufwerk",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
16,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"verwendet eine von ReactOS nicht unterst\201tzte Formatierung.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
18,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Um ReactOS installieren zu k\224nnen, muss das Setup Programm",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
19,
[USETUP] Fix letter encoding in translation. (#3619) CORE-17545 Fix Clang warning: base/setup/usetup/lang/de-DE.h:1099:24: warning: illegal character encoding in string literal [-Winvalid-source-encoding] "die Partition <E4>ndern, die derzeit als aktiv markiert ist.", ^~~~
2021-04-21 15:55:45 +00:00
"die Partition \204ndern, die derzeit als aktiv markiert ist.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
21,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Folgende Partition wird k\201nftig die aktive Systempartition sein:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
25,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie ENTER, um diesen Vorschlag zu akzeptieren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
27,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie ESC, um manuell eine andere Systempartition festzulegen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
28,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
" Erstellen Sie dazu eine neue Partition oder w\204hlen eine existierende in der folgenden Liste",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
29,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
" der Partitionen auf dem Systemlaufwerk.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
32,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Falls sich noch weitere Betriebssysteme auf die alte Systempartition beziehen,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
33,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"k\224nnen Sie entweder manuell versuchen, diese nachtr\204glich anzupassen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
34,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"oder Sie markieren die alte aktive Partition wieder als aktiv",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
35,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"nachdem das ReactOS Setup abgeschlossen wurde.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
0,
0,
NULL,
0
}
};
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
static MUI_ENTRY deDEConfirmDeleteSystemPartitionEntries[] =
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
8,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Sind Sie sicher, dass Sie die aktive Systempartition l\224schen wollen?",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
10,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Systempartitionen enthalten oft wichtige Diagnose-Programme oder",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
11,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Ger\204tetreiber, die ben\224tigt werden, um den Computer starten",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
12,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"oder einen fr\201heren Zustand wiederherstellen zu k\224nnen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
14,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"L\224schen Sie die aktive Systempartition nur falls Sie sicher sind,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
15,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"dass sich keine derartigen Programme auf dieser Partition befinden oder",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
16,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"dass Sie keinerlei Daten von dieser Partition l\204nger ben\224tigen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
17,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Erst nach Abschluss des Setup wird der Computer wieder startf\204hig sein.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
20,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie ENTER, um die aktive Systempartition zu l\224schen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
21,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
" Das L\224schen der Partition muss ein weiteres Mal best\204tigt werden.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
24,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"\x07 Dr\201cken Sie ESC, um zur vorherigen Seite zur\201ckzukehren.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
25,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
" Die Partition wird nicht gel\224scht.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
0,
0,
NULL,
0
}
};
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
static MUI_ENTRY deDEFormatPartitionEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Formatierung der Partition",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
6,
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
2023-10-25 20:19:39 +00:00
16,
[USETUP] de-DE Split a line of text into two parts CORE-16791
2020-04-06 15:11:45 +00:00
"Die gew\201nschte Partition wird nun formatiert.",
TEXT_STYLE_NORMAL,
TEXT_ID_FORMAT_PROMPT
},
{
6,
12,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Dr\201cken Sie ENTER, um fortzusetzen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_FORMAT_PROMPT
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
[USETUP] Remove redundant TEXT_STYLE_NORMAL flag on empty MUI entry field (#2275)
2020-01-26 16:38:58 +00:00
0
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
}
};
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
static MUI_ENTRY deDECheckFSEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
6,
8,
"Die ausgew\204hlte Partition wird \201berpr\201ft.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
0,
0,
"Bitte warten...",
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
static MUI_ENTRY deDEInstallDirectoryEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Die Installationsdateien werden auf die ausgew\204hlte Partition kopiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
6,
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"W\204hlen Sie ein Installationsverzeichnis f\201r ReactOS:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
6,
14,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Geben Sie den Namen des Verzeichnisses an.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
6,
15,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Benutzen Sie die R\201ck-TASTE, um Zeichen zu l\224schen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
},
[USETUP] Add the create logical partition page. svn path=/trunk/; revision=63574
2014-06-09 01:49:24 +00:00
{
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
6,
17,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Best\204tigen Sie die Eingabe mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY deDEFileCopyEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
0,
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Die ben\224tigten Dateien werden in das Installationsverzeichnis kopiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
0,
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
13,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Dieser Vorgang kann einige Zeit in Anspruch nehmen -",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
0,
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
14,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Bitte haben Sie einen Moment Geduld.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
50,
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
0,
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
"\xB3 Bitte warten... ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
static MUI_ENTRY deDEBootLoaderSelectPageEntries[] =
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
"Bestimmen Sie, wo Setup den Bootloader installieren soll:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
12,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Bootloader auf der Festplatte installieren (MBR und VBR)",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
13,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Bootloader auf der Festplatte installieren (nur VBR)",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
14,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Bootloader auf einer Diskette installieren",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] - Add the option to write only the VBR so FreeLoader can easily be chain loaded by GRUB or another boot loader - Dedicated to James Tabor :) svn path=/trunk/; revision=48703
2010-09-05 17:09:18 +00:00
},
{
8,
15,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Bootloader nicht installieren",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen F3 = Abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
static MUI_ENTRY deDEBootLoaderInstallPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
{
6,
8,
"Setup installiert den Bootloader.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
{
0,
0,
[USETUP] Update de-DE Translate the Copying-bootloader status bar text that was added during 0.4.15-dev'ing
2021-06-21 05:37:58 +00:00
"Bootloader wird installiert. Bitte warten...",
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
static MUI_ENTRY deDEBootLoaderRemovableDiskPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
6,
8,
"Der Bootsektor konnte nicht auf der Festplatte Ihres Computers",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
9,
"installiert werden.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
13,
"Bitte legen Sie eine formatierte Diskette in Laufwerk A: ein",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
14,
"und dr\201cken Sie ENTER.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
0,
0,
"ENTER = Fortsetzen F3 = Installation abbrechen",
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
static MUI_ENTRY deDEKeyboardSettingsEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie wollen den zu installierenden Tastaturtyp \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Benutzen Sie die PFEILTASTEN, um den gew\201nschten Typ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" zu w\204hlen. Best\204tigen Sie Ihre Auswahl mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie ESC, um zur vorherigen Seite zur\201ckzukehren,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Fixed a bunch of errors in German USetup Variation svn path=/trunk/; revision=31426
2007-12-24 23:21:41 +00:00
},
{
8,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ohne den Tastaturtyp zu \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Abbrechen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY deDELayoutSettingsEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Bitte w\204hlen Sie das Standardtastaturlayout aus.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Benutzen Sie die PFEILTASTEN, um den gew\201nschten Typ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
11,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" zu w\204hlen. Best\204tigen Sie Ihre Auswahl mit ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie ESC, um zur vorherigen Seite zur\201ckzukehren,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- fix typos, grammar, style and identation svn path=/trunk/; revision=31327
2007-12-19 14:50:21 +00:00
},
{
8,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ohne das Tastaturlayout zu \204ndern.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Abbrechen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY deDEPrepareCopyEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Der Computer wird f\201r die Installation vorbereitet.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
Update Polish and German Resources of USetup. Now working according to recent chnages. Polish Update by Olaf Siejka. svn path=/trunk/; revision=32737
2008-03-21 21:11:09 +00:00
"Erstelle Liste der zu kopierenden Dateien...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY deDESelectFSEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"W\204hlen Sie ein Dateisystem aus der folgenden Liste aus.",
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
0
},
{
8,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie die PFEILTASTEN, um das Dateisystem zu \204ndern.",
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
0
},
{
8,
21,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"\x07 Dr\201cken Sie ENTER, um die Partition zu formatieren.",
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
0
},
{
8,
23,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Dr\201cken Sie ESC, um eine andere Partition auszuw\204hlen.",
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
0
},
{
0,
0,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen ESC = Zur\201ck F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY deDEDeletePartitionEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie haben sich entschieden, diese Partition zu l\224schen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
18,
[USETUP] Use "L" key instead of "D" for deleting partitions at 1st setup stage
2019-06-28 13:45:32 +00:00
"\x07 Dr\201cken Sie L, um die Partition zu l\224schen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
11,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Warnung: Alle Daten auf dieser Partition werden gel\224scht!",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
8,
21,
"\x07 ESC um abzubrechen.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
[USETUP] Use "L" key instead of "D" for deleting partitions at 1st setup stage
2019-06-28 13:45:32 +00:00
"L = L\224sche Partition ESC = Abbrechen F3 = Installation abbrechen",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
0,
0,
NULL,
0
}
};
- Add missing REGISTRY_PAGE localizations note: "make usetup_clean" may be required svn path=/trunk/; revision=31564
2008-01-02 15:07:27 +00:00
static MUI_ENTRY deDERegistryEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
- Add missing REGISTRY_PAGE localizations note: "make usetup_clean" may be required svn path=/trunk/; revision=31564
2008-01-02 15:07:27 +00:00
},
{
6,
8,
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
"Systemkonfiguration wird aktualisiert.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
- Add missing REGISTRY_PAGE localizations note: "make usetup_clean" may be required svn path=/trunk/; revision=31564
2008-01-02 15:07:27 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Registrierungseintr\204ge erstellen...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
- Add missing REGISTRY_PAGE localizations note: "make usetup_clean" may be required svn path=/trunk/; revision=31564
2008-01-02 15:07:27 +00:00
},
{
0,
0,
NULL,
0
},
};
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
MUI_ERROR deDEErrorEntries[] =
{
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{
// NOT_AN_ERROR
"Erfolg\n"
},
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NOT_INSTALLED
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS wurde nicht vollst\204ndig auf Ihrem System installiert.\n"
"Wenn Sie die Installation jetzt beenden, m\201ssen Sie diese\n"
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"erneut starten, um ReactOS zu installieren.\n"
Win32k: - Read from HKCU\Keyboard Layout\Preload for getting the keyboard layout ID to use instead of using the default locale. This finally makes it possible to set the keyboard layout and system locale independently. - Change ReadRegistryValue from KEY_ALL_ACCESS to KEY_READ, we don't need more rights. usetup: - Rename "ProcessKeyboardLayoutRegistry" to "ProcessLocaleRegistry" as it doesn't set anything related to keyboard layouts. - Add a new function "ProcessKeyboardLayoutRegistry", which sets the keyboard layout ID in the correct registry key. - Add ERROR_UPDATE_LOCALE_SETTINGS - Fix the indentation of some parts of the language headers and update the german one. Known issues: - Before input.dll is finished, we can only set the keyboard layout in usetup or by manually editing the registry. - 1st stage and 2nd stage setup always use US English keyboard layout for now. See issue #2635 for more details. svn path=/trunk/; revision=31655
2008-01-07 21:34:56 +00:00
"\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" \x07 Dr\201cken Sie ENTER, um die Installation fortzusetzen.\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \x07 Dr\201cken Sie F3, um die Installation zu beenden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"F3 = Beenden ENTER = Fortsetzen"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
{
// ERROR_NO_BUILD_PATH
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Die Installationspfade f\201r das ReactOS Installationsverzeichnis konnten nicht erstellt werden!\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
},
{
// ERROR_SOURCE_PATH
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Die Partition kann nicht gel\224scht werden, weil sie die Installationsquellen beherbergt!\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
},
{
// ERROR_SOURCE_DIR
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"ReactOS kann nicht in dasselbe Verzeichnis installiert werden, in dem die Installationsquellen liegen!\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
},
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_HDD
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Es konnte keine Festplatte gefunden werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_SOURCE_DRIVE
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Es konnte kein Installationsmedium gefunden werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_TXTSETUPSIF
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"TXTSETUP.SIF konnte nicht gefunden werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CORRUPT_TXTSETUPSIF
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"TXTSETUP.SIF scheint besch\204digt zu sein.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_SIGNATURE_TXTSETUPSIF,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Es wurde eine ung\201ltige Signatur in TXTSETUP.SIF gefunden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DRIVE_INFORMATION
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Es konnten keine Laufwerksinformationen abgefragt werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_BOOT,
[USETUP] Display the chosen filesystem name in case of bootcode installation failure. Simplified implementation of the proposed solution by George Bișoc and revised by Victor Perevertkin from PR #952. NOTE: For whatever reason ERROR_INSTALL_BOOTCODE and ERROR_WRITE_BOOT seem to be redundant with each other. To be investigated...
2018-11-07 23:54:59 +00:00
"Der %S-Bootcode konnte nicht auf der Partition installiert werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_COMPUTER,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Computertypenliste konnte nicht geladen werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_DISPLAY,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Displayeinstellungsliste konnte nicht geladen werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KEYBOARD,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Tastaturtypenliste konnte nicht geladen werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KBLAYOUT,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Liste der Tastaturlayouts konnte nicht geladen werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WARN_PARTITION,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Es wurde mindestens eine Festplatte mit einer inkompatiblen\n"
"Partitionstabelle gefunden, die nicht richtig verwendet werden kann.\n"
Win32k: - Read from HKCU\Keyboard Layout\Preload for getting the keyboard layout ID to use instead of using the default locale. This finally makes it possible to set the keyboard layout and system locale independently. - Change ReadRegistryValue from KEY_ALL_ACCESS to KEY_READ, we don't need more rights. usetup: - Rename "ProcessKeyboardLayoutRegistry" to "ProcessLocaleRegistry" as it doesn't set anything related to keyboard layouts. - Add a new function "ProcessKeyboardLayoutRegistry", which sets the keyboard layout ID in the correct registry key. - Add ERROR_UPDATE_LOCALE_SETTINGS - Fix the indentation of some parts of the language headers and update the german one. Known issues: - Before input.dll is finished, we can only set the keyboard layout in usetup or by manually editing the registry. - 1st stage and 2nd stage setup always use US English keyboard layout for now. See issue #2635 for more details. svn path=/trunk/; revision=31655
2008-01-07 21:34:56 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\216nderungen an den Partitionen k\224nnen die Partitionstabelle zerst\224ren!\n"
Win32k: - Read from HKCU\Keyboard Layout\Preload for getting the keyboard layout ID to use instead of using the default locale. This finally makes it possible to set the keyboard layout and system locale independently. - Change ReadRegistryValue from KEY_ALL_ACCESS to KEY_READ, we don't need more rights. usetup: - Rename "ProcessKeyboardLayoutRegistry" to "ProcessLocaleRegistry" as it doesn't set anything related to keyboard layouts. - Add a new function "ProcessKeyboardLayoutRegistry", which sets the keyboard layout ID in the correct registry key. - Add ERROR_UPDATE_LOCALE_SETTINGS - Fix the indentation of some parts of the language headers and update the german one. Known issues: - Before input.dll is finished, we can only set the keyboard layout in usetup or by manually editing the registry. - 1st stage and 2nd stage setup always use US English keyboard layout for now. See issue #2635 for more details. svn path=/trunk/; revision=31655
2008-01-07 21:34:56 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \x07 Dr\201cken Sie F3, um die Installation zu beenden.\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" \x07 Dr\201cken Sie ENTER, um die Installation fortzusetzen.",
"F3 = Beenden ENTER = Fortsetzen"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NEW_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie k\224nnen keine neue Partition in einer bereits\n"
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"vorhandenen Partition erstellen!\n"
Win32k: - Read from HKCU\Keyboard Layout\Preload for getting the keyboard layout ID to use instead of using the default locale. This finally makes it possible to set the keyboard layout and system locale independently. - Change ReadRegistryValue from KEY_ALL_ACCESS to KEY_READ, we don't need more rights. usetup: - Rename "ProcessKeyboardLayoutRegistry" to "ProcessLocaleRegistry" as it doesn't set anything related to keyboard layouts. - Add a new function "ProcessKeyboardLayoutRegistry", which sets the keyboard layout ID in the correct registry key. - Add ERROR_UPDATE_LOCALE_SETTINGS - Fix the indentation of some parts of the language headers and update the german one. Known issues: - Before input.dll is finished, we can only set the keyboard layout in usetup or by manually editing the registry. - 1st stage and 2nd stage setup always use US English keyboard layout for now. See issue #2635 for more details. svn path=/trunk/; revision=31655
2008-01-07 21:34:56 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * * Eine beliebige Taste zum Fortsetzen dr\201cken.",
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
NULL
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DELETE_SPACE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie k\224nnen unpartitionierten Speicher nicht l\224schen!\n"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Eine beliebige Taste zum Fortsetzen dr\201cken.",
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
NULL
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INSTALL_BOOTCODE,
[USETUP] Display the chosen filesystem name in case of bootcode installation failure. Simplified implementation of the proposed solution by George Bișoc and revised by Victor Perevertkin from PR #952. NOTE: For whatever reason ERROR_INSTALL_BOOTCODE and ERROR_WRITE_BOOT seem to be redundant with each other. To be investigated...
2018-11-07 23:54:59 +00:00
"Der %S-Bootcode konnte nicht auf der Partition installiert werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_FLOPPY,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Keine Diskette in Laufwerk A: gefunden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_KBSETTINGS,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Das Tastaturlayout konnte nicht aktualisiert werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_DISPLAY_SETTINGS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Die Registrierungseintr\204ge der Anzeigeeinstellungen\n"
[USETUP] Add the create logical partition page. svn path=/trunk/; revision=63574
2014-06-09 01:49:24 +00:00
"konnten nicht aktualisiert werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_IMPORT_HIVE,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Es konnte keine Hive-Datei importiert werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_FIND_REGISTRY
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Registrierungsdateien konnten nicht gefunden werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_HIVE,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Zweige in der Registrierung konnten nicht erstellt werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INITIALIZE_REGISTRY,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Registrierung konnte nicht initialisiert werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INVALID_CABINET_INF,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Das CAB-Archiv besitzt keine g\201ltige INF-Datei.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_MISSING,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Das CAB-Archiv wurde nicht gefunden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SCRIPT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Das CAB-Archiv enth\204lt kein Setup-Skript.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_COPY_QUEUE,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Liste mit den zu kopierenden Dateien\n"
[USETUP] Add the create logical partition page. svn path=/trunk/; revision=63574
2014-06-09 01:49:24 +00:00
"konnte nicht gefunden werden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_DIR,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Installationspfade konnten nicht erstellt werden.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_TXTSETUP_SECTION,
"Setup konnte die '%S'-Sektion in\n"
"TXTSETUP.SIF nicht finden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SECTION,
"Setup konnte die '%S'-Sektion im\n"
"CAB-Archiv nicht finden.\n",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_INSTALL_DIR
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
"Setup konnte den Installationspfad nicht erstellen.",
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_PTABLE,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Partitionstabellen konnten nicht geschrieben werden.\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
},
- Added ACP, OEMCP and MACCP keys to registry - Added ERROR_ADDING_CODEPAGE to all languages - Update Russian translation svn path=/trunk/; revision=31642
2008-01-07 14:51:42 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_CODEPAGE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Es konnte kein Codepage-Eintrag hinzugef\201gt werden.\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
Win32k: - Read from HKCU\Keyboard Layout\Preload for getting the keyboard layout ID to use instead of using the default locale. This finally makes it possible to set the keyboard layout and system locale independently. - Change ReadRegistryValue from KEY_ALL_ACCESS to KEY_READ, we don't need more rights. usetup: - Rename "ProcessKeyboardLayoutRegistry" to "ProcessLocaleRegistry" as it doesn't set anything related to keyboard layouts. - Add a new function "ProcessKeyboardLayoutRegistry", which sets the keyboard layout ID in the correct registry key. - Add ERROR_UPDATE_LOCALE_SETTINGS - Fix the indentation of some parts of the language headers and update the german one. Known issues: - Before input.dll is finished, we can only set the keyboard layout in usetup or by manually editing the registry. - 1st stage and 2nd stage setup always use US English keyboard layout for now. See issue #2635 for more details. svn path=/trunk/; revision=31655
2008-01-07 21:34:56 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_LOCALESETTINGS,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Systemsprache konnte nicht eingestellt werden.\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
- Added ACP, OEMCP and MACCP keys to registry - Added ERROR_ADDING_CODEPAGE to all languages - Update Russian translation svn path=/trunk/; revision=31642
2008-01-07 14:51:42 +00:00
},
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_KBLAYOUTS,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Die Tastaturlayouts konnten nicht in die Registrierung\n"
"eingetragen werden.\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
},
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_GEOID,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Der geografische Standort konnte nicht eingestellt werden.\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
- Set geographical position in conjunction with language selection - Translation for the changes made for English and German (other languages need to be updated) - List of languages extend by GeoID-field and set the GeoID for a lot of countries (Some countries needs to update in hivesft_* first, some language entries needs to split up for different countries) - Solves second part of issue #3448, now correct GeoID is set per default for a lot of countries. svn path=/trunk/; revision=39409
2009-02-05 13:50:49 +00:00
},
[USETUP] - Add german translation of required minimum disk space warning. svn path=/trunk/; revision=47342
2010-05-24 21:08:06 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DIRECTORY_NAME,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Unzul\204ssiger Verzeichnisname.\n"
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Eine beliebige Taste zum Fortsetzen dr\201cken."
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INSUFFICIENT_PARTITION_SIZE,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"Die gew\204hlte Partition ist nicht gro\341 genug, um ReactOS zu installieren.\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Die Installationspartition muss mindestens %lu MB gro\341 sein.\n"
[USETUP] - Re-enable the partition size check and display a warning if the install partition is too small. - Update the required install partition size to 550MB. svn path=/trunk/; revision=65847
2014-12-27 12:33:59 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Eine beliebige Taste zum Fortsetzen dr\201cken.",
[USETUP] - Add german translation of required minimum disk space warning. svn path=/trunk/; revision=47342
2010-05-24 21:08:06 +00:00
NULL
},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_PARTITION_TABLE_FULL,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie k\224nnen keine weitere prim\204re oder erweiterte Partition in\n"
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"der Partitionstabelle erstellen, weil die Tabelle voll ist.\n"
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Eine beliebige Taste zum Fortsetzen dr\201cken."
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ONLY_ONE_EXTENDED,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sie k\224nnen nur eine erweiterte Partition auf jeder Festplatte anlegen.\n"
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Eine beliebige Taste zum Fortsetzen dr\201cken."
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
},
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_FORMATTING_PARTITION,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
"Setup konnte die Partition nicht formatieren:\n"
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
" %S\n"
"\n"
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
},
[USETUP] - Add german translation of required minimum disk space warning. svn path=/trunk/; revision=47342
2010-05-24 21:08:06 +00:00
{
Updated German USetup localisation. (Not tested yet, if the string are too long.) svn path=/trunk/; revision=31247
2007-12-15 16:21:12 +00:00
NULL,
NULL
}
};
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
MUI_PAGE deDEPages[] =
{
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
{
SETUP_INIT_PAGE,
deDESetupInitPageEntries
},
- Allow LANGUAGE_PAGE localization - Use DefaultLanguage setting to set the user interface language even for the language selection itself - Add missing language page entries to current localizations, translators get to work! svn path=/trunk/; revision=31437
2007-12-25 20:24:19 +00:00
{
LANGUAGE_PAGE,
deDELanguagePageEntries
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
[USETUP] Massage the USETUP interface code. - The "intro" page is renamed into the "Welcome" page, because its corresponding resource indeed is the welcome screen; - Because the "setup start" page can only be displayed once, move it out of the while-loop, and use its result as the initial value of the 'Page' variable. - Remove unneeded _PAGE_NUMBER_DEFINED guards; - Add a DPRINT in the RepairUpdateFlag case of RegistryPage() (because we don't implement yet a correct upgrading or repairing of the registry). - In InstallIntroPage(), display the page itself only if needed (i.e. after all the validation checks & repair/update or unattended checks are done). Similar modifications are done also in DeviceSettingsPage(), SelectPartitionPage() - Turn both CheckUnattendedSetup() and UpdateKBLayout() into static functions. - Fix the code of ScsiControllerPage() so that it can be compiled if needed, and add a dummy OemDriverPage(). svn path=/branches/setup_improvements/; revision=74575
2017-05-15 01:48:19 +00:00
WELCOME_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEWelcomePageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
- fix a bug showing the same dialog twice in rev 31173 See issue #2888 for more details. svn path=/trunk/; revision=31205
2007-12-13 23:11:24 +00:00
INSTALL_INTRO_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEIntroPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
LICENSE_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDELicensePageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
DEVICE_SETTINGS_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEDevicePageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
REPAIR_INTRO_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDERepairPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
{
UPGRADE_REPAIR_PAGE,
deDEUpgradePageEntries
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
COMPUTER_SETTINGS_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEComputerPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
DISPLAY_SETTINGS_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEDisplayPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
FLUSH_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEFlushPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
SELECT_PARTITION_PAGE,
deDESelectPartitionEntries
},
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
{
CHANGE_SYSTEM_PARTITION,
deDEChangeSystemPartition
},
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
{
CONFIRM_DELETE_SYSTEM_PARTITION_PAGE,
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
deDEConfirmDeleteSystemPartitionEntries
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
SELECT_FILE_SYSTEM_PAGE,
deDESelectFSEntries
},
{
FORMAT_PARTITION_PAGE,
deDEFormatPartitionEntries
},
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
{
CHECK_FILE_SYSTEM_PAGE,
deDECheckFSEntries
},
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
{
DELETE_PARTITION_PAGE,
deDEDeletePartitionEntries
},
{
INSTALL_DIRECTORY_PAGE,
deDEInstallDirectoryEntries
},
{
PREPARE_COPY_PAGE,
deDEPrepareCopyEntries
},
{
FILE_COPY_PAGE,
deDEFileCopyEntries
},
{
KEYBOARD_SETTINGS_PAGE,
deDEKeyboardSettingsEntries
},
{
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
BOOTLOADER_SELECT_PAGE,
deDEBootLoaderSelectPageEntries
- move nearly all hardcoded strings to the language specific files - translate the new imported strings for german resource - put all moved string for all other languages - remove country identifier for languages which only has currently one translation (english/french) svn path=/trunk/; revision=31326
2007-12-19 14:29:39 +00:00
},
{
LAYOUT_SETTINGS_PAGE,
deDELayoutSettingsEntries
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
QUIT_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDEQuitPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
{
SUCCESS_PAGE,
- implement displaying and showing language dialog - rename all translated entries in de-DE.h because gcc doesnt understand the scope of static - add basic language dialog - feel free to improve design, layout etc svn path=/trunk/; revision=31200
2007-12-13 16:15:43 +00:00
deDESuccessPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
{
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
BOOTLOADER_INSTALL_PAGE,
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
deDEBootLoaderInstallPageEntries
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
BOOTLOADER_REMOVABLE_DISK_PAGE,
deDEBootLoaderRemovableDiskPageEntries
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
},
- Add missing REGISTRY_PAGE localizations note: "make usetup_clean" may be required svn path=/trunk/; revision=31564
2008-01-02 15:07:27 +00:00
{
REGISTRY_PAGE,
deDERegistryEntries
},
German Translation for usetup. svn path=/trunk/; revision=31193
2007-12-13 15:01:21 +00:00
{
-1,
NULL
}
};
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
MUI_STRING deDEStrings[] =
{
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_PLEASEWAIT,
" Bitte warten..."},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{STRING_INSTALLCREATEPARTITION,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" ENTER = Installieren C = Prim\204re E = Erweiterte F3 = Installation abbr."},
[USETUP] - Add status text for logical partition entries in the partition list. - Add logical partition creation page dummy. svn path=/trunk/; revision=63570
2014-06-08 19:05:03 +00:00
{STRING_INSTALLCREATELOGICAL,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" ENTER = Installieren C = Logische Partition F3 = Installation abbrechen"},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{STRING_INSTALLDELETEPARTITION,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" ENTER = Installieren D = Partition l\224schen F3 = Installation abbrechen"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_DELETEPARTITION,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
" D = Partition l\224schen F3 = Installation abbrechen"},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{STRING_PARTITIONSIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Gr\224\341e der neuen Partition:"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_CHOOSE_NEW_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Eine prim\204re Partition soll hier erstellt werden:"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_CHOOSE_NEW_EXTENDED_PARTITION,
"Eine erweiterte Partition soll hier erstellt werden:"},
[USETUP] Add the create logical partition page. svn path=/trunk/; revision=63574
2014-06-09 01:49:24 +00:00
{STRING_CHOOSE_NEW_LOGICAL_PARTITION,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
"Eine logische Partition soll hier erstellt werden:"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDPARTSIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Bitte geben Sie die Gr\224\341e der neuen Partition in Megabyte ein."},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{STRING_CREATEPARTITION,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" ENTER = Partition erstellen ESC = Abbrechen F3 = Installation abbrechen"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_NEWPARTITION,
"Setup erstellte eine neue Partition auf"},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_PARTFORMAT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Diese Partition wird als n\204chstes formatiert."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_NONFORMATTEDPART,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Sie wollen ReactOS auf einer neuen/unformatierten Partition installieren."},
[USETUP] - Implement mandatory filesystem selection, formatting and filesystem checks for all new partitons. - Implement optional filesystem selection, formatting and filesystem checks for formatted boot and install partitions. - Enable installing ReactOS on primary partitions other than the first one. Usetup will install Freeloader on the first (or active) partition (aka boot partition) and install ReactOS on the chosen partition (aka install partition). svn path=/trunk/; revision=68112
2015-06-12 21:51:57 +00:00
{STRING_NONFORMATTEDSYSTEMPART,
[USETUP] Update german language header. svn path=/trunk/; revision=68114
2015-06-12 23:37:41 +00:00
"Die Systempartition ist noch nicht formartiert."},
[USETUP] - Implement mandatory filesystem selection, formatting and filesystem checks for all new partitons. - Implement optional filesystem selection, formatting and filesystem checks for formatted boot and install partitions. - Enable installing ReactOS on primary partitions other than the first one. Usetup will install Freeloader on the first (or active) partition (aka boot partition) and install ReactOS on the chosen partition (aka install partition). svn path=/trunk/; revision=68112
2015-06-12 21:51:57 +00:00
{STRING_NONFORMATTEDOTHERPART,
[USETUP] Update german language header. svn path=/trunk/; revision=68114
2015-06-12 23:37:41 +00:00
"Die neue Partition ist noch nicht formatiert."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_INSTALLONPART,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"ReactOS wird auf dieser Partition installiert."},
[USETUP]: In case chkdsk detects some disk errors, just display a warning message but allow the user to continue the installation. svn path=/trunk/; revision=70857
2016-03-02 00:51:48 +00:00
{STRING_CONTINUE,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Fortsetzen"},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_QUITCONTINUE,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"F3 = Beenden ENTER = Fortsetzen"},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_REBOOTCOMPUTER,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
"ENTER = Computer neu starten"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_DELETING,
" Deleting file: %S"},
{STRING_MOVING,
" Moving file: %S to: %S"},
{STRING_RENAMING,
" Renaming file: %S to: %S"},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{STRING_COPYING,
[USETUP] Made the 'Copying file...' status line message left aligned like all the other status line messages. svn path=/trunk/; revision=47343
2010-05-24 21:43:51 +00:00
" Kopiere Datei: %S"},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{STRING_SETUPCOPYINGFILES,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
"Dateien werden kopiert..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_REGHIVEUPDATE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" Registrierungseintr\204ge werden aktualisiert..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_IMPORTFILE,
" Importiere %S..."},
[USETUP] Resources: fix a typo. svn path=/branches/setup_improvements/; revision=75748
2017-09-03 12:08:39 +00:00
{STRING_DISPLAYSETTINGSUPDATE,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
" Anzeigeeinstellungen werden aktualisiert..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_LOCALESETTINGSUPDATE,
" Lokalisierungseinstellungen werden aktualisiert..."},
{STRING_KEYBOARDSETTINGSUPDATE,
Giant German Language Fix Patch by "tux." I skipped xcopy, winhlp32 and wordpad because they are wine synched and expand, because its not translated anymore. Fix some BOMs i did not see at wine synching. svn path=/trunk/; revision=45501
2010-02-08 19:35:26 +00:00
" Tastaturlayouteinstellungen werden aktualisiert..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_CODEPAGEINFOUPDATE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" Codepage-Informationen werden hinzugef\201gt..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_DONE,
" Fertig..."},
{STRING_REBOOTCOMPUTER2,
[USETUP] de-DE Update 2022-03-05 CORE-18075 Avoids some typos like gew\201nste -> gew\201nschte gew\204hlten -> gew\204hlte Global replacement of fahr->setz to harmonize the mixed usage of Fortfahren vs Fortsetzen Also recently someone started using ENTER instead of EINGABETASTE and although I was pissed off by that in the beginning, after thinking twice: ENTER is the much better alternative to EINGABETASTE, because: - it does not need to be translated from english - it is shorter and therefore helps to avoid some needed abbreviations - it allows to avoid articles and therefore aligns better with other selections - it avoids translation errors like EINGABETASTER (and EEINGABETASTE in older branches) So I use that consistently throughout the translation now. Also shorten "Der PC wird automatisch neu gestartet" because that line was so long, that it looked odd. 88 Lines touched: "Der Führer wär stolz"
2022-03-05 17:23:33 +00:00
" ENTER = Computer neu starten"},
[USETUP] Implement the shutdown timeout progress bar. (#833) - Add the MUI ID resource. - Implement the shutdown timeout progress bar function and the TimeOut string handler. - Add the resource string to other resource languages.
2018-08-22 09:10:18 +00:00
{STRING_REBOOTPROGRESSBAR,
[USETUP] de-DE Overhaul german translation CORE-16792
2020-04-06 18:49:44 +00:00
" Der Computer wird in %li Sekunde(n) neugestartet... "},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_CONSOLEFAIL1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Konsole konnte nicht ge\224ffnet werden\r\n\r\n"},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_CONSOLEFAIL2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Der h\204ufigste Grund hierf\201r ist die Verwendung einer USB-Tastatur\r\n"},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_CONSOLEFAIL3,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"USB-Tastaturen werden noch nicht vollst\204ndig unterst\201tzt\r\n"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_FORMATTINGPART,
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
2023-10-25 20:19:39 +00:00
"Die Partition wird formatiert..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_CHECKINGDISK,
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
2023-10-25 20:19:39 +00:00
"Die Festplatte wird \201berpr\201ft..."},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_FORMATDISK1,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
" Partition mit dem %S-Dateisystem formatieren (Schnell) "},
Beginnings to allow to translate all other Strings. Translators, PLEEASE wait until I am ready before you file Bugs, you can already start to translate, but do not post Bugreports until I am ready adding the last hidden ones. Thanks to Johannes Anderwald for explaining me why it made more Problems than fix stuff to translate some strings and how to fix it. svn path=/trunk/; revision=32322
2008-02-12 14:52:36 +00:00
{STRING_FORMATDISK2,
[TRANSLATIONS] Applications: some corrections and improvements to German translations by zehnvor CORE-8130 #resolve #comment Committed, thx. usetup: German translation revamp by zehnvor CORE-8179 #resolve #comment Committed, thx. DLL: Many improvements to German translations by zehnvor (without the dll patch yet, Wine syncs need no ROS only tranlation IMO) CORE-8216 #comment Committed without the dll patch yet, Wine syncs need no ROS only tranlation IMO svn path=/trunk/; revision=63275
2014-05-13 18:11:07 +00:00
" Partition mit dem %S-Dateisystem formatieren "},
Hopefully the last String. Translators. Your turn. svn path=/trunk/; revision=32325
2008-02-12 17:00:09 +00:00
{STRING_KEEPFORMAT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" Dateisystem beibehalten (Keine Ver\204nderungen) "},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDISK1,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
"%s."},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDISK2,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
"auf %s."},
{STRING_PARTTYPE,
"Typ 0x%02x"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDINFO1,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
// "Festplatte %lu (%I64u %s), Port=%hu, Bus=%hu, Id=%hu (%wZ) [%s]"
"%I64u %s Festplatte %lu (Port=%hu, Bus=%hu, Id=%hu) auf %wZ [%s]"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDINFO2,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
// "Festplatte %lu (%I64u %s), Port=%hu, Bus=%hu, Id=%hu [%s]"
"%I64u %s Festplatte %lu (Port=%hu, Bus=%hu, Id=%hu) [%s]"},
Once more... make it possible to translate usetup COMPLETELY. (I hope this time I am right....) svn path=/trunk/; revision=32392
2008-02-16 18:58:05 +00:00
{STRING_UNPSPACE,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
"Unpartitionierter Speicher"},
Once more, some more Strings open for translation. Have fun with 'em. svn path=/trunk/; revision=32423
2008-02-19 19:37:49 +00:00
{STRING_MAXSIZE,
"MB (max. %lu MB)"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_EXTENDED_PARTITION,
"Erweiterte Partition"},
Once more, some more Strings open for translation. Have fun with 'em. svn path=/trunk/; revision=32423
2008-02-19 19:37:49 +00:00
{STRING_UNFORMATTED,
"Neu (Unformatiert)"},
{STRING_FORMATUNUSED,
"Ungenutzt"},
{STRING_FORMATUNKNOWN,
"Unbekannt"},
Okokok, I dont know why someone should feel the urge to translate MB, KB, and GB (Except specific languages...), but here they are. svn path=/trunk/; revision=32427
2008-02-19 21:31:09 +00:00
{STRING_KB,
"KB"},
{STRING_MB,
"MB"},
{STRING_GB,
"GB"},
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
{STRING_ADDKBLAYOUTS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Tastaturlayout hinzuf\201gen"},
- allow translation of strings in usetup - so far most strings are still hardcoded, but the needed functionality is in place svn path=/trunk/; revision=32204
2008-02-08 04:14:09 +00:00
{0, 0}
};
Reference in a new issue Copy permalink