Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2024-07-21 11:48:04 +00:00
Code Issues Packages Projects Releases Wiki Activity
reactos/base/setup/usetup/lang/fr-FR.h

2373 lines
51 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 frFRSetupInitPageEntries[] =
{
{
4,
3,
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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,
"Veuillez patienter pendant que le programme d'installation de 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_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,
"s'initialise et d\202couvre vos p\202riph\202riques...",
[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,
"Veuillez patienter...",
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 frFRLanguagePageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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,
[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
"S\202lection de la langue.",
[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 Veuiller choisir la langue utilis\202e pour le processus d'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
},
{
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
" et appuyer sur ENTR\220E.",
[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 Cette langue sera la langue par d\202faut pour le syst\212me final.",
[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][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
"ENTR\220E = Continuer F3 = Quitter",
[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
}
};
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
static MUI_ENTRY frFRWelcomePageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
6,
8,
[USETUP]: French translation for extended partitions feature, see r63392. svn path=/trunk/; revision=63393
2014-05-21 00:18:50 +00:00
"Bienvenue dans l'installation de 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_HIGHLIGHT,
TEXT_ID_STATIC
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
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
"Cette partie de l'installation copie le Syst\212me d'Exploitation 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
12,
[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
"sur votre ordinateur et le pr\202pare \205 la 2\212me partie de l'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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"\x07 Appuyer sur ENTR\220E pour installer ou mettre \205 jour 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
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
"\x07 Appuyer sur R pour r\202parer 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
19,
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
"\x07 Appuyer sur L pour les Termes et Conditions de Licence 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
21,
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
"\x07 Appuyer sur F3 pour quitter sans installer 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
23,
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
"Pour plus d'informations sur ReactOS, veuiller visiter :",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Continuer R = R\202parer L = Licence F3 = Quitter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRIntroPageEntries[] =
{
{
4,
3,
[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
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
8,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"Statut de version de 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_HIGHLIGHT,
TEXT_ID_STATIC
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"ReactOS est en version Alpha, ce qui signifie qu'il n'est pas complet",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
12,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"et est en cours de d\202veloppement. Il est recommand\202 de ne l'utiliser",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
13,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"que pour \202valuation et test, pas pour un usage quotidien.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
15,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"Sauvegardez vos donn\202es ou testez sur un ordinateur secondaire",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
16,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"si vous souhaitez utiliser ReactOS sur du mat\202riel.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"\x07 Appuyez sur ENTR\220E pour continuer l'installation de 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"\x07 Appuyez sur F3 pour quitter sans installer 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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"ENTR\220E = Continuer F3 = Quitter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRLicensePageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
6,
6,
Fixed some details svn path=/trunk/; revision=31279
2007-12-16 15:25:17 +00:00
"Licence :",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
8,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"Le syst\212me ReactOS est distribu\202 sous les termes de",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
9,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"la licence GNU GPL avec des parties contenant du code sous",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
10,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"d'autres licences compatibles telles que X11, BSD et GNU LGPL.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
11,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"Tout le logiciel constituant le syst\212me ReactOS est",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
12,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"par cons\202quent distribu\202 sous licence GNU GPL tout en",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
13,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"maintenant la licence d'origine.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
15,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"Ce logiciel vient SANS GARANTIE ou restriction d'usage",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
16,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"sous les lois locales ou internationales applicables.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
17,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"La licence de ReactOS ne couvre que la distribution",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
18,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"aux tierces parties.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
19,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"Si vous n'avez pas obtenu une copie de la",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
20,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
"GNU General Public License avec ReactOS veuillez visiter",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
8,
21,
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
"http://www.gnu.org/licenses/licenses.html",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
23,
Fixed some details svn path=/trunk/; revision=31279
2007-12-16 15:25:17 +00:00
"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_HIGHLIGHT,
TEXT_ID_STATIC
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
25,
"Ce logiciel est gratuit. Voir les sources pour les",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
26,
"conditions de copie.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
[SETUP] French translation of missing elements (#3111) Co-authored-by: Hermès BÉLUSCA - MAÏTO <hermes.belusca-maito@reactos.org>
2020-09-03 19:20:54 +00:00
27,
"Il n'y a AUCUNE garantie; pas m\210me sur la QUALIT\220 ou",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
8,
28,
"l'AD\220QUATION POUR UN USAGE EN PARTICULIER",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Retour",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRDevicePageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"La liste ci-dessous montre les r\202glages mat\202riels actuels.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
11,
Fixed some details svn path=/trunk/; revision=31279
2007-12-16 15:25:17 +00:00
" Ordinateur :",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
12,
Fixed some details svn path=/trunk/; revision=31279
2007-12-16 15:25:17 +00:00
" Affichage :",
- Allow multiple combination of style flags for usetup translations - Added right & center text align , no more space counting :). All localization can now share X,Y cordinates Note: only the en-US localization currently takes advantage of it , other localizations should be updated svn path=/trunk/; revision=32722
2008-03-19 04:43:40 +00:00
TEXT_STYLE_NORMAL,
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
13,
Fixed some details svn path=/trunk/; revision=31279
2007-12-16 15:25:17 +00:00
" Clavier :",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
8,
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
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
"R\202glage Clavier :",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
16,
Fixed some details svn path=/trunk/; revision=31279
2007-12-16 15:25:17 +00:00
" Accepter :",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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, "Accepter ces r\202glages mat\202riels",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Vous pouvez changer les r\202glages mat\202riels en appuyant sur HAUT ou BAS",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
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
"pour s\202lectionner une entr\202e.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
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
"Appuyer sur ENTR\220E pour choisir un autre r\202glage.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Quand tous les r\202glages sont corrects, s\202lectionner \"Accepter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
24,
[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
"ces r\202glages mat\202riels\" et appuyer sur ENTR\220E.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Continuer F3 = Quitter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRRepairPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"L'installation de ReactOS est en phase de d\202veloppement.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
9,
"Elle ne supporte pas encore toutes les fonctions d'une application",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
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
"d'installation enti\212rement utilisable.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Les fonctions de r\202paration ne sont pas impl\202ment\202es pour l'instant.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"\x07 Appuyer sur U pour mettre \205 jour l'OS.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
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
"\x07 Appuyer sur R pour la Console de R\202paration.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 Appuyer sur \220CHAP pour revenir \205 la page principale.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 Appuyer sur ENTR\220E pour red\202marrer votre ordinateur.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"\220CHAP = Page principale ENTR\220E = Red\202marrer",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 frFRUpgradePageEntries[] =
{
{
4,
3,
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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][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
"Le programme d'installation de ReactOS peut mettre \205 jour l'une des",
[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][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
"installations de ReactOS list\202es ci-dessous, ou bien, si l'une d'elles",
[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][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
"est endommag\202e, le programme d'installation peut essayer de la r\202parer.",
[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][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
"Les fonctions de r\202paration ne sont pas toutes impl\202ment\202es.",
[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][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 Appuyer sur HAUT ou BAS pour s\202lectionner une 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
[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][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 Appuyer sur U pour mettre \205 jour l'installation s\202lectionn\202e.",
[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][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 Appuyer sur \220CHAP pour effectuer une nouvelle 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
[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,
"\x07 Appuyer sur F3 pour quitter sans installer 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
[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][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
"U = Mettre \205 jour \220CHAP = Annuler F3 = Quitter",
[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
}
};
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
static MUI_ENTRY frFRComputerPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Vous voulez changer le type d'ordinateur install\202.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 Appuyer sur HAUT ou BAS pour s\202lectionner le type d'ordinateur.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
" Puis appuyer sur ENTR\220E.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 Appuyer sur \220CHAP pour revenir \205 la page pr\202c\202dente sans changer",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
8,
14,
" le type d'ordinateur.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Continuer \220CHAP = Annuler F3 = Quitter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRFlushPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Le syst\212me s'assure que toutes les donn\202es sont \202crites sur le disque.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
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
"Cela peut prendre une minute.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
9,
[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
"Quand cela sera fini, votre ordinateur red\202marrera automatiquement.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
[USETUP] - Fix a bit the translation of yesterday; - Use TEXT_PADDING_BIG instead of hardcoding 3 spaces in the status messages. svn path=/trunk/; revision=63398
2014-05-21 12:23:04 +00:00
"Vidage du cache",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRQuitPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 n'est pas compl\212tement install\202.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
8,
"Enlever la disquette du lecteur A: et",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
9,
"tous les CDROMs des lecteurs de CD.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
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
"Appuyer sur ENTR\220E pour red\202marrer votre ordinateur.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Veuillez patienter...",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRDisplayPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Vous voulez changer le type d'\202cran \205 installer.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 Appuyer sur HAUT ou BAS pour s\202lectionner le type d'\202cran.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
" Appuyer sur ENTR\220E.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 Appuyer sur \220CHAP pour revenir \205 la page pr\202c\202dente sans changer",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
" le type d'\202cran.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Continuer \220CHAP = Annuler F3 = Quitter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRSuccessPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
10,
6,
[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
"Les composants standards de ReactOS ont \202t\202 install\202s avec succ\212s.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
8,
"Enlever la disquette du lecteur A: et",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
9,
"tous les CDROMs des lecteurs de CD.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
10,
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
"Appuyer sur ENTR\220E pour red\202marrer votre ordinateur.",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Red\202marrer l'ordinateur",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY frFRBootPageEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
6,
8,
"Setup ne peut installer le chargeur sur le disque dur",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
9,
"de votre ordinateur",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
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
"Veuillez ins\202rer une disquette format\202e dans le lecteur A: et",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
6,
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
"appuyer sur ENTR\220E.",
- Allow multiple combination of style flags for usetup translations - Added right & center text align , no more space counting :). All localization can now share X,Y cordinates Note: only the en-US localization currently takes advantage of it , other localizations should be updated svn path=/trunk/; revision=32722
2008-03-19 04:43:40 +00:00
TEXT_STYLE_NORMAL,
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"ENTR\220E = Continuer F3 = Quitter",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 frFRSelectPartitionEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
"La liste suivante montre les partitions existantes et",
[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
"l'espace disque non utilis\202 pour de nouvelles partitions.",
[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 Appuyer sur HAUT ou BAS pour s\202lectionner une entr\202e de la 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
- 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 Appuyer sur ENTR\220E pour installer ReactOS sur la partition choisie.",
[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][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 Appuyer sur P pour cr\202er une partition primaire.",
[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][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 Appuyer sur E pour cr\202er une partition \202tendue.",
[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 Appuyer sur L pour cr\202er une partition logique.",
[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 description of the 'L' key to the partition selection page. - Make the 'ENTER' key work for logical partitions too. Selected unpartitioned space will be converted to a logical partition. Patch by Gerhard Gruber (sparhawk). CORE-9641 #resolve svn path=/trunk/; revision=68339
2015-07-04 16:04:09 +00:00
},
{
8,
21,
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
"\x07 Appuyer sur D pour effacer une 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,
[USETUP] - Fix a bit the translation of yesterday; - Use TEXT_PADDING_BIG instead of hardcoding 3 spaces in the status messages. svn path=/trunk/; revision=63398
2014-05-21 12:23:04 +00:00
"Patienter...",
[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 frFRChangeSystemPartition[] =
{
{
4,
3,
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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,
"La partition syst\212me actuelle de votre ordinateur",
[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,
"sur le disque syst\212me",
[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,
"emploie un format qui n'est pas support\202 par 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
[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,
"Afin de pouvoir installer ReactOS avec succ\212s, ReactOS Setup doit changer",
[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,
"la partition syst\212me actuelle par une nouvelle.",
[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,
"La nouvelle partition syst\212me candidate est :",
[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,
"\x07 Pour accepter ce choix, appuyez sur ENTR\220E.",
[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,
"\x07 Pour changer manuellement la partition syst\212me, appuyez sur \220CHAP",
[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,
" afin de revenir dans la liste des partitions, puis s\202lectionnez ou",
[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,
" cr\202ez une nouvelle partition syst\212me sur le disque syst\212me.",
[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,
"S'il existe d'autres syst\212mes d'exploitation qui d\202pendent de la 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,
33,
"syst\212me d'origine, vous devrez peut-\210tre les reconfigurer pour la nouvelle",
[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,
"partition syst\212me, ou bien changer la partition syst\212me vers celle",
[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,
"d'origine apr\212s la fin de l'installation de 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
[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,
"ENTR\220E = Continuer \220CHAP = Annuler",
[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 frFRConfirmDeleteSystemPartitionEntries[] =
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,
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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][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
"Vous avez choisi de supprimer la partition syst\212me.",
[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][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
"La partition syst\212me peut contenir des programmes de diagnostic, de",
[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][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
"configuration du mat\202riel, des programmes pour d\202marrer un syst\212me",
[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]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
"d'exploitation (comme ReactOS) ou d'autres programmes fournis par le",
[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,
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
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
"constructeur du mat\202riel.",
[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][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
"Ne supprimez la partition syst\212me que si vous \210tes s\226r qu'il n'y a aucun",
[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]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
"programme dans la partition, ou bien si vous souhaitez les supprimer.",
[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][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
"Lorsque vous supprimez la partition syst\212me, vous ne pourrez peut-\210tre",
[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]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
},
{
6,
18,
[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
"plus d\202marrer votre ordinateur depuis le disque dur jusqu'\205 ce que vous",
[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]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
},
{
6,
19,
"finissiez l'installation de 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
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,
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
22,
[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 Appuyer sur ENTR\220E pour supprimer la partition syst\212me. Il vous sera",
[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,
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
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
" demand\202 de confirmer la suppression de la partition plus tard.",
[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,
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
26,
[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 Appuyer sur \220CHAP pour revenir \205 la page principale. La 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
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,
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
27,
[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
" ne sera pas supprim\202e.",
[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][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
"ENTR\220E = Continuer \220CHAP = Annuler",
[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 frFRFormatPartitionEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
"Formater la 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
},
{
6,
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
"Setup va formater la partition. Appuyer sur ENTR\220E pour continuer.",
[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][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
"ENTR\220E = Continuer F3 = Quitter",
[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 frFRCheckFSEntries[] =
{
{
4,
3,
" Installation de ReactOS " KERNEL_VERSION_STR " ",
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
6,
8,
"Setup v\202rifie la partition s\202lectionn\202e.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
0,
0,
"Veuillez patienter...",
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 frFRInstallDirectoryEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
"Setup installe les fichiers de ReactOS sur la partition s\202lectionn\202e.",
[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
"Choisissez un repertoire o\227 vous voulez que ReactOS soit install\202 :",
[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,
[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
"Pour changer le r\202pertoire propos\202, appuyez sur BACKSPACE pour effacer",
[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
"des caract\212res et ensuite tapez le r\202pertoire ou vous voulez que",
[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,
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
"ReactOS soit install\202",
[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][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
"ENTR\220E = Continuer F3 = Quitter",
[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 frFRFileCopyEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
{
11,
12,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
"Patientez pendant que ReactOS Setup copie les fichiers",
[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
},
{
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
15,
- 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,
[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
"dans le r\202pertoire d'installation de 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
},
{
20,
14,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
"Cela peut prendre plusieurs minutes.",
[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 french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
" \xB3 Patientez... ",
[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
}
};
static MUI_ENTRY frFRBootLoaderEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
"Setup installe le chargeur de d\202marrage",
[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,
[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
"Installer le chargeur de d\202marrage sur le disque dur (MBR et 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,
[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
"Installer le chargeur de d\202marrage sur le disque dur (VBR seulement).",
[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,
[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
"Installer le chargeur de d\202marrage sur une disquette.",
[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,
[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
"Ne pas installer le chargeur de d\202marrage.",
[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][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
"ENTR\220E = Continuer F3 = Quitter",
[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 frFRBootLoaderInstallPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
0,
0,
"Installing the bootloader onto the media, please wait...",
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 frFRKeyboardSettingsEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
"Vous voulez changer le type de clavier \205 installer.",
[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 Appuyez sur HAUT ou BAS pour s\202lectionner le type de clavier,",
[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
" puis appuyez sur ENTR\220E.",
[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 Appuyez sur \220CHAP pour revenir \205 la page pr\202c\202dente sans changer",
[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,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
" le type de clavier.",
[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][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
"ENTR\220E = Continuer \220CHAP = Annuler F3 = Quitter",
[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 frFRLayoutSettingsEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
"Veuillez s\202lectionner une disposition \205 installer par d\202faut.",
[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 Appuyez sur HAUT ou BAS pour s\202lectionner la disposition",
[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
" choisie. Puis appuyez sur ENTR\220E.",
[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 Appuyez sur \220CHAP pour revenir \205 la page pr\202c\202dente sans changer",
[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,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
" la disposition du clavier.",
[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][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
"ENTR\220E = Continuer \220CHAP = Annuler F3 = Quitter",
[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 frFRPrepareCopyEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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] 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 pr\202pare votre ordinateur pour copier les fichiers de 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
},
{
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
"Pr\202pare la liste de fichiers \205 copier...",
[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 frFRSelectFSEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
"S\202lectionnez un syst\212me de fichiers dans la liste suivante.",
- 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 Appuyez sur HAUT ou BAS pour s\202lectionner un syst\212me de fichiers.",
- 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][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 Appuyez sur ENTR\220E pour formater la partition.",
- 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 Appuyez sur \220CHAP pour s\202lectionner une autre partition.",
- 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][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
"ENTR\220E = Continuer \220CHAP = Annuler F3 = Quitter",
[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 frFRDeletePartitionEntries[] =
{
Allow usetup page title localization svn path=/trunk/; revision=31524
2007-12-31 17:56:13 +00:00
{
4,
3,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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,
update french translation for usetup remove accentuated characters for now svn path=/trunk/; revision=31392
2007-12-22 13:10:44 +00:00
"Vous avez choisi de supprimer la 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,
18,
[USETUP] Use "L" key instead of "D" for deleting partitions at 1st setup stage
2019-06-28 13:45:32 +00:00
"\x07 Appuyez sur L pour supprimer la 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
},
{
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
"ATTENTION: Toutes les donne\202es de cette partition seront perdues!",
[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,
[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 Appuyez sur \220CHAP pour annuler.",
[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,
[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
"L = Supprimer la partition \220CHAP = Annuler F3 = Quitter",
[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 frFRRegistryEntries[] =
{
{
4,
3,
[USETUP] Finish to translate "ReactOS xxxxx Setup". svn path=/trunk/; revision=57827
2012-12-08 21:09:57 +00:00
" Installation de ReactOS " KERNEL_VERSION_STR " ",
[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
"Setup met \205 jour la configuration du syst\212me.",
[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
- 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
"En train de cr\202er la base de registres...",
[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
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
MUI_ERROR frFRErrorEntries[] =
{
[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
[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
"Succ\212s\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
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 n'est pas compl\212tement install\202 sur votre\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
"ordinateur. Si vous quittez Setup maintenant, vous devrez\n"
"lancer Setup de nouveau pour installer ReactOS.\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
" \x07 Appuyer sur ENTR\220E pour continuer Setup.\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
" \x07 Appuyer sur F3 pour quitter Setup.",
[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
"F3 = Quitter ENTR\220E = Continuer"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
{
// ERROR_NO_BUILD_PATH
"Failed to build the installation paths for the ReactOS installation directory!\n"
"ENTER = Reboot computer"
},
{
// ERROR_SOURCE_PATH
"You cannot delete the partition containing the installation source!\n"
"ENTER = Reboot computer"
},
{
// ERROR_SOURCE_DIR
"You cannot install ReactOS within the installation source directory!\n"
"ENTER = Reboot computer"
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu trouver un disque dur.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu trouver son lecteur source.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
[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
"Setup n'a pas r\202ussi \205 charger le fichier TXTSETUP.SIF.\n",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Setup a trouv\202 un fichier TXTSETUP.SIF corrompu.\n",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Setup a trouv\202 une signature invalide dans TXTSETUP.SIF.\n",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
[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
"Setup n'a pu r\202cup\202rer les informations du disque syst\212me.\n",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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][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
"Echec de l'installation du code de d\202marrage %S sur la partition syst\212me.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu charger la liste de type d'ordinateurs.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Setup n'a pu charger la liste de r\202glages des \202crans.\n",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu charger la liste de types de claviers.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu charger la liste de dispositions de claviers.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Setup a d\202tect\202 qu'au moins un disque dur contient une table\n"
"de partition incompatible qui ne peut \210tre prise en compte!\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
"Cr\202er ou effacer des partitions peut d\202truire la table de partition.\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] fix layout issue in invalid partition error message svn path=/trunk/; revision=61648
2014-01-16 20:31:51 +00:00
" \x07 Appuyer sur F3 pour quitter Setup.\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 Appuyer sur ENTR\220E pour continuer Setup.",
"F3 = Quitter ENTR\220E = Continuer"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Vous ne pouvez cr\202er une nouvelle partition \205 l'int\202rieur\n"
"d'une partition d\202j\205 existante!\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 french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
" * Appuyer sur une touche pour continuer.",
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Vous ne pouvez supprimer de l'espace disque non partitionn\202!\n"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
"\n"
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
" * Appuyer sur une touche pour continuer.",
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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][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
"Echec de l'installation du code de d\202marrage %S sur la partition syst\212me.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Pas de disque dans le lecteur A:.",
[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
"ENTR\220E = Continuer"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Setup n'a pu mettre \205 jour les r\202glages de disposition du clavier.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Setup n'a pu mettre \205 jour les r\202glages de l'\202cran.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu importer un fichier ruche.",
[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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu trouver les fichiers de la base de registres.",
[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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Setup n'a pu cr\202er les ruches de la base de registres.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Setup n'a pu initialiser la base de registres.",
[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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Le Cabinet n'a pas de fichier inf valide.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Cabinet non trouv\202.\n",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"Cabinet n'a pas de script de setup.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
usetup french translation update, now taking advantage of vga font. svn path=/trunk/; revision=31948
2008-01-22 17:58:33 +00:00
"Setup n'a pu ouvrir la file d'attente de copie de fichiers.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Setup n'a pu cr\202er les r\202pertoires d'installation.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 n'a pu trouver la section '%S'\n"
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"dans TXTSETUP.SIF.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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 n'a pu trouver la section '%S\n"
usetup: translate error codes, fix a typo svn path=/trunk/; revision=31526
2007-12-31 18:29:49 +00:00
"dans le cabinet.\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
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
[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
"Setup n'a pu cr\202er le r\202pertoire d'installation.",
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
[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
"Setup n'a pu \202crire les tables de partition.\n"
"ENTR\220E = Red\202marrer l'ordinateur"
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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
"Setup n'a pu ajouter la page de codes \205 la base de registres.\n"
"ENTR\220E = Red\202marrer l'ordinateur"
- 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
},
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,
[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
"Setup n'a pu changer la langue syst\212me.\n"
"ENTR\220E = Red\202marrer l'ordinateur"
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
},
- 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,
[USETUP] - Translation updates by Pierre Schweitzer. svn path=/trunk/; revision=48718
2010-09-07 09:40:53 +00:00
"Setup n'a pas pu ajouter les dispositions de clavier au registre.\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
"ENTR\220E = Red\202marrer l'ordinateur"
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
},
[usetup] - The last error messages were swapped in some languages, spotted by Paolo Devoti. - Added the minimum required disk space also in the debug print. See issue #5440 for more details. svn path=/trunk/; revision=47524
2010-06-02 22:28:37 +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,
[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
"Setup n'a pas pu d\202finir la geo id.\n"
"ENTR\220E = Red\202marrer l'ordinateur"
[usetup] - The last error messages were swapped in some languages, spotted by Paolo Devoti. - Added the minimum required disk space also in the debug print. See issue #5440 for more details. svn path=/trunk/; revision=47524
2010-06-02 22:28:37 +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_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
"Nom de r\202pertoire invalide.\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"
" * Appuyer sur une touche pour continuer."
},
[USETUP] - Check for required minimum disk space eventually warn the user. - Added Italian and Spanish warnings, the other languages need translation. - Patch by R.T.Sivakumar modified by me. See issue #3302 for more details. svn path=/trunk/; revision=47341
2010-05-24 20:53: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] - 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
"The selected partition is not large enough to install ReactOS.\n"
"The install partition must have a size of at least %lu MB.\n"
"\n"
[USETUP]: French translation for extended partitions feature, see r63392. svn path=/trunk/; revision=63393
2014-05-21 00:18:50 +00:00
" * Appuyer sur une touche pour continuer.",
[USETUP] - Check for required minimum disk space eventually warn the user. - Added Italian and Spanish warnings, the other languages need translation. - Patch by R.T.Sivakumar modified by me. See issue #3302 for more details. svn path=/trunk/; revision=47341
2010-05-24 20:53:32 +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
"Impossible de cr\202er une nouvelle partition primaire ou \202tendue\n"
[USETUP]: French translation for extended partitions feature, see r63392. svn path=/trunk/; revision=63393
2014-05-21 00:18:50 +00:00
"sur ce disque parce que sa table de partition est pleine.\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]: French translation for extended partitions feature, see r63392. svn path=/trunk/; revision=63393
2014-05-21 00:18:50 +00:00
" * Appuyer sur une touche pour continuer."
[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
"Impossible de cr\202er plus d'une partition \202tendue par disque.\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]: French translation for extended partitions feature, see r63392. svn path=/trunk/; revision=63393
2014-05-21 00:18:50 +00:00
" * Appuyer sur une touche pour continuer."
[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] 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
"Setup is unable to format the partition:\n"
" %S\n"
"\n"
"ENTER = Reboot computer"
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
NULL,
NULL
}
};
MUI_PAGE frFRPages[] =
{
[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,
frFRSetupInitPageEntries
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
LANGUAGE_PAGE,
- 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
frFRLanguagePageEntries
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +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,
- Fix typo svn path=/trunk/; revision=31561
2008-01-02 13:50:37 +00:00
frFRWelcomePageEntries
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
},
{
INSTALL_INTRO_PAGE,
frFRIntroPageEntries
},
{
LICENSE_PAGE,
frFRLicensePageEntries
},
{
DEVICE_SETTINGS_PAGE,
frFRDevicePageEntries
},
{
REPAIR_INTRO_PAGE,
frFRRepairPageEntries
},
[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,
frFRUpgradePageEntries
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
COMPUTER_SETTINGS_PAGE,
frFRComputerPageEntries
},
{
DISPLAY_SETTINGS_PAGE,
frFRDisplayPageEntries
},
{
FLUSH_PAGE,
frFRFlushPageEntries
},
- 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,
frFRSelectPartitionEntries
},
[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,
frFRChangeSystemPartition
},
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
frFRConfirmDeleteSystemPartitionEntries
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,
frFRSelectFSEntries
},
{
FORMAT_PARTITION_PAGE,
frFRFormatPartitionEntries
},
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
{
CHECK_FILE_SYSTEM_PAGE,
frFRCheckFSEntries
},
- 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,
frFRDeletePartitionEntries
},
{
INSTALL_DIRECTORY_PAGE,
frFRInstallDirectoryEntries
},
{
PREPARE_COPY_PAGE,
frFRPrepareCopyEntries
},
{
FILE_COPY_PAGE,
frFRFileCopyEntries
},
{
KEYBOARD_SETTINGS_PAGE,
frFRKeyboardSettingsEntries
},
{
BOOT_LOADER_PAGE,
frFRBootLoaderEntries
},
{
LAYOUT_SETTINGS_PAGE,
frFRLayoutSettingsEntries
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
QUIT_PAGE,
frFRQuitPageEntries
},
{
SUCCESS_PAGE,
frFRSuccessPageEntries
},
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
{
BOOT_LOADER_INSTALLATION_PAGE,
frFRBootLoaderInstallPageEntries
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
BOOT_LOADER_FLOPPY_PAGE,
frFRBootPageEntries
},
- 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,
frFRRegistryEntries
},
french translation for usetup svn path=/trunk/; revision=31250
2007-12-15 16:52:40 +00:00
{
-1,
NULL
}
};
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
MUI_STRING frFRStrings[] =
{
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,
" Veuillez patienter..."},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{STRING_INSTALLCREATEPARTITION,
[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
" ENTR\220E = Installer P/E = Cr\202er partition Primaire/\220tendue F3 = Quitter"},
[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,
[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
" ENTR\220E = Installer L = Cr\202er partition Logique F3 = Quitter"},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{STRING_INSTALLDELETEPARTITION,
[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
" ENTR\220E = Installer D = Supprimer partition F3 = Quitter"},
[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,
[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
" D = Supprimer partition F3 = Quitter"},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{STRING_PARTITIONSIZE,
"Taille de la nouvelle partition :"},
{STRING_CHOOSENEWPARTITION,
[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
"Vous avez choisi de cr\202er une partition primaire sur"},
[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,
[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
"Vous avez choisi de cr\202er une partition \202tendue sur"},
[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][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
"Vous avez choisi de cr\202er une partition logique sur"},
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_HDDSIZE,
[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
"Veuillez entrer la taille de la nouvelle partition en m\202gaoctets."},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{STRING_CREATEPARTITION,
[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
" ENTR\220E = Cr\202er partition \220CHAP = Annuler F3 = Quitter"},
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,
[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
"Cette partition sera ensuite format\202e."},
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,
french usetup translation update see complete filenames when "Copying file :" svn path=/trunk/; revision=32408
2008-02-17 19:56:37 +00:00
"Vous avez choisi d'installer ReactOS sur une nouvelle partition."},
[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,
[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
"La partition syst\212me n'est pas encore format\202e."},
[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,
[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
"La nouvelle partition n'est pas encore format\202e."},
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,
french usetup translation update see complete filenames when "Copying file :" svn path=/trunk/; revision=32408
2008-02-17 19:56:37 +00:00
"Setup installe ReactOS sur la partition"},
[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][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
"ENTR\220E = Continuer"},
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][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
"F3 = Quitter ENTR\220E = Continuer"},
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][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
"ENTR\220E = Red\202marrer l'ordinateur"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_DELETING,
" Suppression du fichier : %S"},
{STRING_MOVING,
[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
" D\202placement du fichier : %S vers : %S"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_RENAMING,
" Renommage du fichier : %S vers : %S"},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{STRING_COPYING,
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
" Copie du fichier : %S"},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{STRING_SETUPCOPYINGFILES,
"Setup copie les fichiers..."},
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
" Mise \205 jour de la base de registre..."},
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,
french usetup translation update see complete filenames when "Copying file :" svn path=/trunk/; revision=32408
2008-02-17 19:56:37 +00:00
" Importe %S..."},
[USETUP] Resources: fix a typo. svn path=/branches/setup_improvements/; revision=75748
2017-09-03 12:08:39 +00:00
{STRING_DISPLAYSETTINGSUPDATE,
[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
" Mise \205 jour des param\212tres du registre pour l'\202cran..."},
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,
[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
" Mise \205 jour des param\212tres r\202gionaux..."},
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_KEYBOARDSETTINGSUPDATE,
[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
" Mise \205 jour des param\212tres de la dispoition clavier..."},
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
" Ajout des informations de pages de codes \205 la base de registres..."},
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,
[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
" Termin\202..."},
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_REBOOTCOMPUTER2,
[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
" ENTR\220E = Red\202marrer l'ordinateur"},
[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][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
" Votre ordinateur va red\202marrer dans %li seconde(s)... "},
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]: The STRING_CONSOLEFAIL1/2/3 are aimed to be printed with NtDisplayString, which will use InbvDisplayString. Therefore add \r with \n. Part 2/X svn path=/trunk/; revision=60655
2013-10-13 23:18:22 +00:00
"Impossible d'ouvrir la console\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]: The STRING_CONSOLEFAIL1/2/3 are aimed to be printed with NtDisplayString, which will use InbvDisplayString. Therefore add \r with \n. Part 2/X svn path=/trunk/; revision=60655
2013-10-13 23:18:22 +00:00
"La cause probable est l'utilisation d'un clavier USB\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
"Les claviers USB ne sont pas compl\212tement support\202s actuellement\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_FORMATTINGDISK,
french usetup translation update see complete filenames when "Copying file :" svn path=/trunk/; revision=32408
2008-02-17 19:56:37 +00:00
"Setup formate votre disque"},
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][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
"Setup v\202rifie votre disque"},
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,
[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
" Formater la partition comme syst\212me de fichiers %S (formatage rapide) "},
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,
[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
" Formater la partition comme syst\212me de fichiers %S "},
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
" Garder le syst\212me de fichiers courant (pas de changements) "},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTCREATE_1,
[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 of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTDELETE_1,
[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
"sur le %s."},
{STRING_PARTTYPE,
"Type 0x%02x"},
{STRING_HDDINFO_1,
// "Disque dur %lu (%I64u %s), Port=%hu, Bus=%hu, Id=%hu (%wZ) [%s]"
"%I64u %s Disque dur %lu (Port=%hu, Bus=%hu, Id=%hu) sur %wZ [%s]"},
{STRING_HDDINFO_2,
// "Disque dur %lu (%I64u %s), Port=%hu, Bus=%hu, Id=%hu [%s]"
"%I64u %s Disque dur %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_NEWPARTITION,
[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
"Setup a cr\202\202 une nouvelle partition sur"},
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
"Espace non partitionn\202"},
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,
- Update French translation svn path=/trunk/; revision=32425
2008-02-19 19:56:35 +00:00
"Mo (max. %lu Mo)"},
[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,
[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
"Partition \220tendue"},
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,
[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
"Nouveau (non format\202)"},
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_FORMATUNUSED,
[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
"Non utilis\202"},
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_FORMATUNKNOWN,
- Update French translation svn path=/trunk/; revision=32425
2008-02-19 19:56:35 +00:00
"Inconnu"},
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,
"Ko"},
{STRING_MB,
"Mo"},
{STRING_GB,
"Go"},
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
{STRING_ADDKBLAYOUTS,
[USETUP] - Translation updates by Pierre Schweitzer. svn path=/trunk/; revision=48718
2010-09-07 09:40:53 +00:00
"Ajout des dispositions clavier"},
Updated French translations for : - desk.cpl - mmsys.cpl - usetup.exe svn path=/trunk/; revision=32235
2008-02-09 10:34:00 +00:00
{0, 0}
};
Reference in a new issue Copy permalink