Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2024-07-06 12:45:16 +00:00
Code Issues Packages Projects Releases Wiki Activity
reactos/base/setup/usetup/lang/ro-RO.h

2382 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>".
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
/* Ștefan Fulea (stefan dot fulea at mail dot com) */
- 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
- Add more languages - Update languages svn path=/trunk/; revision=33814
2008-06-01 17:17:56 +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 roROSetupInitPageEntries[] =
{
{
4,
3,
" Instalare 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"Asteptati initializarea programului de instalare si",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"identificarea dispozitivelor din calculator...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"Asteptati...",
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_ID_STATIC
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
},
{
0,
0,
NULL,
0
}
};
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
static MUI_ENTRY roROLanguagePageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Selec\376ie limb\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Selecta\376i limba pentru procesul de instalare.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Apoi ap\343sa\376i ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Aceasta va fi \356n final limba implicit\343 pentru tot sistemul.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROWelcomePageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
8,
"Bun venit la instalarea 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Aceast\343 prim\343 etap\343 din instalarea ReactOS va copia fi\272ierele",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"necesare \356n calculatorul dumneavoastr\343 \272i-l va preg\343ti pentru",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"cea de-a doua etap\343 a instal\343rii.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
16,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"\x07 Tasta\376i ENTER pentru a instala sau actualiza 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
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
"\x07 Tasta\376i R pentru a reface un sistem deteriorat.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Tasta\376i L pentru Termenii \272i Condi\376iile de Licen\376iere.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
23,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i F3 pentru a ie\272i f\343r\343 a instala 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
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
"Pentru mai multe informa\376ii despre ReactOS, vizita\376i:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
27,
[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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare R = Refacere L = Licen\376\343 F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROIntroPageEntries[] =
{
{
4,
3,
[TRANSLATION] Update Romanian translation (#851) Translation from Stefan Fulea. CORE-15023
2018-09-14 09:04:36 +00:00
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
8,
[TRANSLATION] Update Romanian translation (#851) Translation from Stefan Fulea. CORE-15023
2018-09-14 09:04:36 +00:00
"Starea versiunii curente a 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
11,
[USETUP][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 este \356n stadiu alfa de dezvoltare, adic\343 nu are prezint\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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,
[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
"func\376ionalit\343\376i complete \272i \356nc\343 nu este recomandat\343 utilizarea sa",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ca sistem de operare de zi cu zi. Asigura\376i-v\343 copii ale datelor",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
6,
[USETUP] Remove obsolete restriction info. svn path=/trunk/; revision=68266
2015-06-25 20:20:21 +00:00
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
"\356n cazul \356n care \356ncerca\376i ReactOS \356n mod neemulat.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
6,
[USETUP] Remove obsolete restriction info. svn path=/trunk/; revision=68266
2015-06-25 20:20:21 +00:00
16,
[TRANSLATION] Update Romanian translation (#851) Translation from Stefan Fulea. CORE-15023
2018-09-14 09:04:36 +00:00
"",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ENTER pentru a instala 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i F3 pentru a ie\272i f\343r\343 a instala 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROLicensePageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
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
"Licen\376iere:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
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
"Sistemul de operare ReactOS este oferit \356n termenii Licen\376ei",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
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
"Publice Generale GNU, referit\343 \356n continuare ca GPL, cu p\343r\376i",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"de cod din alte licen\376e compatibile (ca X11, BSD, \272i 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
12,
[TRANSLATIONS] * Massive update of Romanian resources. Brought to you by Ștefan Fulea. CORE-7778 #resolve #comment Committed in r61740. Thanks ! svn path=/trunk/; revision=61740
2014-01-20 19:42:49 +00:00
"Toate componentele care fac parte din sistemul ReactOS sunt",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"prin urmare oferite sub licen\376a GPL, men\376in\342ndu-\272i astfel \272i",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"licen\376ierea original\343 \356n acela\272i timp.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
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
"Acest sistem vine f\343r\343 vreo restric\376ie de utilizare, aceasta",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"fiind o condi\376ie legislativ\343 aplicabil\343 at\342t la nivel local",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
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
"c\342t \272i interna\376ional. Licen\376ierea se refer\343 doar la distri-",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"buirea sistemului ReactOS c\343tre p\343r\376i ter\376e.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +00:00
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
"Dac\343 din vreun careva motiv nu de\376ine\376i o copie a licen\376ei",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +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
"GPL \356mpreun\343 cu ReactOS, o pute\376i consulta (\356n englez\343)",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +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
"acces\342nd pagina:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +00:00
24,
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +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
"Garan\376ie:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +00:00
29,
[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
"Acest sistem de operare este distribuit doar \356n speran\376a c\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +00:00
30,
[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
"va fi util, neav\342nd \356ns\343 ata\272at\343 NICI O GARAN\336IE; nici m\343car",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +00:00
31,
[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
"garan\376ia implicit\343 a VANDABILIT\303\336II sau a UTILIT\303\336II \316NTR-UN",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATIONS] * Massive update of Romanian resources. Brought to you by Ștefan Fulea. CORE-7778 #resolve #comment Committed in r61740. Thanks ! svn path=/trunk/; revision=61740
2014-01-20 19:42:49 +00:00
},
{
8,
[VARIOUS] Romanian resources maintenance Patch by Ștefan Fulea. CORE-10811 #resolve #comment Thanks a lot! svn path=/trunk/; revision=70761
2016-02-20 21:14:13 +00:00
32,
[TRANSLATIONS] * Massive update of Romanian resources. Brought to you by Ștefan Fulea. CORE-7778 #resolve #comment Committed in r61740. Thanks ! svn path=/trunk/; revision=61740
2014-01-20 19:42:49 +00:00
"SCOP ANUME.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
"ENTER = Revenire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roRODevicePageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Configurare dispozitive de baz\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
24,
11,
"Arh. de calcul:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
24,
12,
"Parametri grafici:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
24,
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
"Model tastatur\343:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
24,
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
"Aranj. tastatur\343:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
24,
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
"Accept\343:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
25,
[TRANSLATION] Massive resource maintenance update. 2 oatches by Ștefan Fulea. Thank you! CORE-12326 svn path=/trunk/; revision=73390
2016-11-27 00:15:02 +00:00
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Accept configura\376ia dispozitivelor",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Pute\376i modifica starea curent\343. Utiliza\376i tastele SUS/JOS pentru",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"alegerea unui dispozitiv, apoi ap\343sa\376i ENTER pentru a-i modifica",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"configura\376ia ata\272at\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"C\342nd configura\376ia dispozitivele enumerate este cea corect\343,",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"selecta\376i \"Accept configura\376ia dispozitivelor\", apoi confirma\376i",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
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
"ap\343s\342nd ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roRORepairPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Programul de instalare ReactOS este \356nc\343 \356ntr-o faz\343 incipient\343 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"dezvoltare \272i nu posed\343 o func\376ionalitate complet\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Func\376ionalitatea de refacere \356nc\343 nu este implementat\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Tasta\376i U pentru actualizarea sistemului.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Tasta\376i R pentru consola de Recuperare.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
19,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a reveni la pagina principal\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
21,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ENTER pentru a reporni calculatorul.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
"ESC = Revenire U = Actualizare R = Recuperare ENTER = Repornire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 roROUpgradePageEntries[] =
{
{
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
" Instalare 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"Programul de Instalare ReactOS ofer\343 actualizarea urm\343toarelor instal\343ri",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"existente, sau, dac\343 o instalare este deteriorat\343, programul de instalare",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"poate \356ncerca s\343 o repare.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"Func\376ionalitatea de reparare \356nc\343 nu este complet implementat\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"\x07 Tasta\376i SUS sau JOS pentru a selecta o instalare existent\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"\x07 Tasta\376i U pentru a actualiza instalarea selectat\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"\x07 Tasta\376i ESC pentru a continua cu o nou\343 instalare.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"\x07 Tasta\376i F3 pentru a ie\272i f\343r\343 a instala 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,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
"U = Actualizare ESC = Evitare actualizare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
}
};
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
static MUI_ENTRY roROComputerPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Dori\376i specificarea unei alte arhitecturi de calcul?",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Utiliza\376i tastele SUS/JOS pentru a selecta o",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" arhitectur\343 de calcul, apoi ap\343sa\376i ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
13,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a reveni la pagina precedent\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" f\343r\343 a specifica o alt\343 arhitectur\343 de calcul.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare ESC = Anulare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROFlushPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Sistemul verific\343 integritatea datelor scrise pe disc.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Aceasta poate dura c\342teva momente.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
9,
[TRANSLATIONS] * Romanian translations update by Ștefan Fulea. CORE-8520 svn path=/trunk/; revision=64721
2014-10-13 15:24:08 +00:00
"La final, calculatorul va fi repornit automat.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
[TRANSLATION] Massive resource maintenance update. 2 oatches by Ștefan Fulea. Thank you! CORE-12326 svn path=/trunk/; revision=73390
2016-11-27 00:15:02 +00:00
"Eliberare memorie...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROQuitPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ReactOS nu a fost instalat \356n \356ntregime.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Scoate\376i discul flexibil din unitatea A:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
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
"\272i toate mediile CD-ROM din unit\343\376ile 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
11,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"Tasta\376i ENTER pentru a reporni calculatorul.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"A\272tepta\376i...",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roRODisplayPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Dori\376i modificarea parametrilor grafici de afi\272are?",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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,
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Utiliza\376i tastele SUS/JOS pentru a selecta",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" un grup de parametri, apoi ap\343sa\376i ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
13,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a reveni la pagina precedent\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
14,
" fara a modifica parametrii grafici actuali.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare ESC = Anulare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROSuccessPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Componentele de baz\343 ale ReactOS au fost instalate cu succes.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Scoate\376i discul flexibil din unitatea A: \272i toate mediile",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
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
"CD-ROM din unit\343\376ile 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
10,
11,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"Tasta\376i ENTER pentru a reporni calculatorul.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
"ENTER = Repornire calculator",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROBootPageEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
8,
[TRANSLATION] Massive resource maintenance update. 2 oatches by Ștefan Fulea. Thank you! CORE-12326 svn path=/trunk/; revision=73390
2016-11-27 00:15:02 +00:00
"Programul de instalare nu poate instala modulul 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ini\376ializare a calculatorului pe discul local.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Introduce\376i un disc flexibil formatat \356n",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"unitatea A: apoi s\343 ap\343sa\376i ENTER.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROSelectPartitionEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Urm\343toarea list\343 cuprinde parti\376iile existente, precum \272i",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"spa\376iul liber disponibil pentru crearea de noi parti\376ii.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Utiliza\376i tastele SUS/JOS pentru a selecta o op\376iune.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
13,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ENTER pentru a instala pe parti\376ia selectat\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Tasta\376i P pentru a crea o parti\376ie primar\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Tasta\376i E pentru a crea o parti\376ie extins\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Tasta\376i L pentru a crea o parti\376ie logic\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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][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 Tasta\376i D pentru a \272terge o parti\376ie existent\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"A\272tepta\376i...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 roROChangeSystemPartition[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
8,
"The current system partition of your computer",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"on the system disk",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"uses a format not supported by 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,
"In order to successfully install ReactOS, the Setup program must change",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"the current system partition to a new one.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"The new candidate system partition is:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 To accept this choice, press ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[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 To manually change the system partition, press ESC to go back to",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
" the partition selection list, then select or create a new system",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
" partition on the system disk.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"In case there are other operating systems that depend on the original",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"system partition, you may need to either reconfigure them for the new",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"system partition, or you may need to change the system partition back",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
"to the original one after finishing the installation of 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,
"ENTER = Continue ESC = Cancel",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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 roROConfirmDeleteSystemPartitionEntries[] =
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
" Instalare 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
"A\376i solicitat \272tergerea parti\376iei de sistem.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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
"Parti\376iile de sistem pot con\376ine programe de diagnoz\343, programe de con-",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Romanian resources maintenance by Ștefan Fulea CORE-10042 #resolve #comment Committed, thx ^^ svn path=/trunk/; revision=69260
2015-09-17 17:26:52 +00:00
"figurare a echipamentelor, programe de lansare a unui sistem de operare",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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][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
"(ca ReactOS) \272i alte programe furnizate de produc\343torii calculorului.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
14,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\252terge\376i o parti\376ie de sistem doar c\342nd fie ave\376i siguran\376a c\343 nu ve\376i",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\272terge accidental a\272a programe pe parti\376ie, fie dori\376i s\343 le \272terge\376i.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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][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
"\252terg\342nd parti\376ia apare riscul de a nu mai putea porni calculatorul 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,
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
"pe discul local dec\342t dup\343 finalizarea instal\343rii 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,
20,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ENTER pentru a \272terge parti\376ia de sistem. Vi se va",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
21,
[USETUP][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
" cere s\343 confirma\376i din nou aceast\343 \272tergere a parti\376iei.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
24,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a reveni la pagina precedent\343. Parti\376ia",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
25,
[USETUP][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
" nu va fi \272tears\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Romanian resources maintenance by Ștefan Fulea CORE-10042 #resolve #comment Committed, thx ^^ svn path=/trunk/; revision=69260
2015-09-17 17:26:52 +00:00
"ENTER = Continuare ESC = Anulare",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
}
};
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
static MUI_ENTRY roROFormatPartitionEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
6,
8,
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
"Urmeaz\343 formatarea parti\376iei. Tasta\376i ENTER pentru a continua.",
TEXT_STYLE_NORMAL,
TEXT_ID_FORMAT_PROMPT
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 roROCheckFSEntries[] =
{
{
4,
3,
" Instalare ReactOS " KERNEL_VERSION_STR " ",
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
6,
8,
"Programul de instalare verific\343 acum parti\376ia aleas\343.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
0,
0,
"A\272tepta\376i...",
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
static MUI_ENTRY roROInstallDirectoryEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Alege\376i un director de instalare pe parti\376ia aleas\343.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Aici vor fi amplasate fi\272ierele sistemului 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Pute\376i indica un alt director, ap\343s\342nd BACKSPACE pentru",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"a \272terge caractere, apoi scriind calea directorului unde",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"dori\376i s\343 instala\376i 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROFileCopyEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
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
"Are loc copierea de fi\272iere \356n directorul ReactOS specificat.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
[TRANSLATION] - Romanian translation update (bug no. 6654) by Stefan Fulea; - Simplified Chineese translation of base/shell and system (bug no. 6655) by Song Fuchang; - Slovak translation fixes (bug no. 6658) by Mario Kacmar; svn path=/trunk/; revision=54399
2011-11-16 20:16:21 +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
"(aceasta poate dura c\342teva momente)",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
50,
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
"\xB3 A\272tepta\376i...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROBootLoaderEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Instalare modul de ini\376ializare al calculatorului",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Instaleaz\343 ini\376ializatorul pe discul intern (MBR \272i 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Instaleaz\343 ini\376ializatorul pe discul intern (doar 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Instaleaz\343 ini\376ializatorul pe un disc flexibil.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Omite instalarea modulului de ini\376ializare.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 roROBootLoaderInstallPageEntries[] =
{
{
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
}
};
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
static MUI_ENTRY roROKeyboardSettingsEntries[] =
{
{
4,
3,
" Instalare 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,
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Dori\376i specificarea modelului tastaturii instalate?",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Utiliza\376i tastele SUS/JOS pentru a selecta un model",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" de tastatur\343, apoi ap\343sa\376i ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
13,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a reveni la pagina precedent\343 f\343r\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
14,
" a schimba modelul tastaturii curente.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare ESC = Anulare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roROLayoutSettingsEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Dori\376i specificarea unui aranjament implicit de tastatur\343?",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Utiliza\376i tastele SUS/JOS pentru a selecta un aranjament",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" dorit de tastatur\343, apoi ap\343sa\376i ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
13,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a reveni la pagina precedent\343 f\343r\343",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
14,
[TRANSLATION] - netid, vmwinst romanian translation, see bug number:6531; - resource updates and corrections in multiple romanian translations, see bug number: 6532; - Patches by Stefan Fulea; [ACLUI] - convert module to ReactOS resource style (separate lang directory); svn path=/trunk/; revision=53998
2011-10-05 00:06:20 +00:00
" a schimba aranjamentul curent al tastaturii.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare ESC = Anulare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY roROPrepareCopyEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Au loc preg\343tirile necesare pentru copierea de fi\272iere.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"List\343 de fi\272iere \356n curs de creare...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY roROSelectFSEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Alege\376i un sistem de fi\272iere din lista de mai jos.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
0
},
{
8,
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Utiliza\376i tastele SUS/JOS pentru a selecta",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
0
},
{
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
" un sistem de fi\272iere.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
0
},
{
8,
19,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ENTER pentru a formata parti\376ia.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
0
},
{
8,
21,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a alege o alt\343 parti\376ie.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ENTER = Continuare ESC = Anulare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roRODeletePartitionEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"A\376i ales s\343 \272terge\376i parti\376ia",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 Tasta\376i L pentru a \272terge parti\376ia.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"ATEN\336IE: Toate datele de pe aceast\343 parti\376ie vor fi pierdute!",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
8,
21,
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
"\x07 Tasta\376i ESC pentru a anula.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
[USETUP] Use "L" key instead of "D" for deleting partitions at 1st setup stage
2019-06-28 13:45:32 +00:00
"L = \252tergere parti\376ie ESC = Anulare F3 = Ie\272ire",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY roRORegistryEntries[] =
{
{
4,
3,
" Instalare 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Are loc actualizarea configura\376iei sistemului.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Registru \356n curs de creare...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
},
{
0,
0,
NULL,
0
},
};
MUI_ERROR roROErrorEntries[] =
{
[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
[TRANSLATION] general maintenance of Romanian resources by Stefan Fuela CORE-8334 #resolve #comment Committed, thx. svn path=/trunk/; revision=63765
2014-07-29 13:17:00 +00:00
"Succes\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
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09: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_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 nu a fost instalat \356n totalitate \356n calculator.\n"
"Dac\343 abandona\376i instalarea acum, alt\343 dat\343, pentru a\n"
"instala ReactOS, va fi nevoie s\343 repeta\376i to\376i pa\272ii.\n"
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"\n"
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
" \x07 Tasta\376i ENTER pentru a continua instalarea.\n"
" \x07 Tasta\376i F3 pentru a abandona instalarea.",
[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 = Ie\272ire ENTER = Continuare"
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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"
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09: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_NO_HDD
[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
"E\272ec la identificarea unit\343\376ilor interne de stocare.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la accesarea unitat\343\376ii de instalare.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la \356nc\343rcarea fi\272ierul TXTSETUP.SIF.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"Fi\272ieul TXTSETUP.SIF a fos g\343sit deteriorat.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"Fi\272ierul TXTSETUP.SIF con\376ine o semn\343tur\343 nevalid\343.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la ob\376inerea de informa\376ii despre\n"
[TRANSLATION] Massive resource maintenance update. 2 oatches by Ștefan Fulea. Thank you! CORE-12326 svn path=/trunk/; revision=73390
2016-11-27 00:15:02 +00:00
"dispozitivele din calculator.\n",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la instalarea codului %S de ini\376ializare\n"
"pe parti\376ia de sistem.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la \356nc\343rcarea listei cu arhitecturi de\n"
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
"calcul disponibile.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la \356nc\343rcarea listei cu parametri de\n"
"afi\272are pentru ecran.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la \356nc\343rcarea listei cu tipuri\n"
"disponibile de tastatur\343.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la \356nc\343rcarea listei de configura\376ii\n"
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
"ale tastaturii.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"A fost g\343sit\343 cel pu\376in un disc cu tabel\343 nerecunoscut\343\n"
"de parti\376ii, care nu poate fi gestionat\343 corespunz\343tor!\n"
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Crearea sau \272tergerea de parti\376ii poate astfel cauza\n"
"distrugerea tabelei de parti\376ii."
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"\n"
[TRANSLATION] Improve the existing translated contents
2019-01-27 19:13:03 +00:00
" \x07 Tasta\376i F3 pentru a abandona instalarea.\n"
" \x07 Tasta\376i ENTER pentru a continua.",
[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 = Ie\272ire ENTER = Continuare"
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09: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_NEW_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"O parti\376ie nou\343 nu poate fi creat\343 \356n interiorul\n"
"unei parti\376ii existente!\n"
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" * Tasta\376i pentru a continua.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"A\376i \356ncercat \272tergerea de spa\376iu neparti\376ionat,\n"
"\356ns\343 doar spa\376iul parti\376ionat poate fi \272ters!\n"
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" * Tasta\376i pentru a continua.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"E\272ec la instalarea codului %S de ini\376ializare\n"
"pe parti\376ia de sistem.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"Nu exist\343 discuri flexibile \356n unitatea A:",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Continuare"
},
{
[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
"E\272ec la actualizarea configura\376iei de tastatur\343.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la actualizarea registrului cu\n"
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
"parametrii grafici ai ecranului!",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la importarea registrului.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la localizarea fi\272ierelor\n"
[TRANSLATION] Massive resource maintenance update. 2 oatches by Ștefan Fulea. Thank you! CORE-12326 svn path=/trunk/; revision=73390
2016-11-27 00:15:02 +00:00
"cu datele registrului.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la crearea registrului.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la ini\376ializarea registrului.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INVALID_CABINET_INF,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Fi\272ierul cabinet nu con\376ine nici\n"
"un fi\272ier valid de tip inf.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la localizarea fi\272ierului cabinet.\n",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SCRIPT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Fi\272ierul cabinet nu con\376ine nici\n"
[TRANSLATION] Massive resource maintenance update. 2 oatches by Ștefan Fulea. Thank you! CORE-12326 svn path=/trunk/; revision=73390
2016-11-27 00:15:02 +00:00
"un script de instalare.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la accesarea listei cu\n"
"fi\272iere pentru copiere.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la crearea directoarelor de instalare.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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,
[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
"E\272ec la identificarea sec\376iunii\n"
"'%S' \356n fi\272ierul TXTSETUP.SIF.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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,
[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
"E\272ec la identificarea sec\376iunii\n"
"'%S' \356n fi\272ierul cabinet.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la crearea directorului de instalare.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la scrierea tabelelor de parti\376ii.\n",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la includerea pagin\343rii \356n registru.\n",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la instituirea sistemului de localizare.\n",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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][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
"E\272ec la includerea \356n registru a configura\376iei\n"
"de tastatur\343.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
{
[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
"E\272ec la instituirea de geo id.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
"ENTER = Repornire calculator"
},
[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,
[TRANSLATIONS] Romanian translation update by Ștefan Fulea. CORE-9516 svn path=/trunk/; revision=67139
2015-04-10 19:20:55 +00:00
"Numele de director este nevalid.\n"
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Tasta\376i pentru a continua."
[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
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09: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_INSUFFICIENT_PARTITION_SIZE,
[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
"Parti\376ia selectat\343 este prea mic\343 pentru a instala ReactOS.\n"
"Parti\376ia de instalare trebuie s\343 aib\343 cel pu\376in %lu Mocte\376i.\n"
[USETUP] - Re-enable the partition size check and display a warning if the install partition is too small. - Update the required install partition size to 550MB. svn path=/trunk/; revision=65847
2014-12-27 12:33:59 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Tasta\376i pentru a continua.",
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Nu poate fi creat\343 o nou\343 parti\376ie primar\343 sau extins\343 \356n tabela\n"
"de parti\376ii a acestui disc deoarece tabela de parti\376ii e plin\343.\n"
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Tasta\376i pentru a continua."
[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
"Nu poate fi creat\343 mai mult de o parti\376ie extins\343 pe un disc.\n"
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * Tasta\376i pentru a continua."
[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][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
"E\272ec la formatarea parti\376iei:\n"
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
" %S\n"
"\n"
[TRANSLATION] Romanian resources maintenance by Ștefan Fulea CORE-10042 #resolve #comment Committed, thx ^^ svn path=/trunk/; revision=69260
2015-09-17 17:26:52 +00:00
"ENTER = Repornire calculator"
[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
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{
NULL,
NULL
}
};
MUI_PAGE roROPages[] =
{
[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,
roROSetupInitPageEntries
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{
LANGUAGE_PAGE,
roROLanguagePageEntries
},
{
[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,
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
roROWelcomePageEntries
},
{
INSTALL_INTRO_PAGE,
roROIntroPageEntries
},
{
LICENSE_PAGE,
roROLicensePageEntries
},
{
DEVICE_SETTINGS_PAGE,
roRODevicePageEntries
},
{
REPAIR_INTRO_PAGE,
roRORepairPageEntries
},
[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,
roROUpgradePageEntries
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{
COMPUTER_SETTINGS_PAGE,
roROComputerPageEntries
},
{
DISPLAY_SETTINGS_PAGE,
roRODisplayPageEntries
},
{
FLUSH_PAGE,
roROFlushPageEntries
},
{
SELECT_PARTITION_PAGE,
roROSelectPartitionEntries
},
[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,
roROChangeSystemPartition
},
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
roROConfirmDeleteSystemPartitionEntries
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
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{
SELECT_FILE_SYSTEM_PAGE,
roROSelectFSEntries
},
{
FORMAT_PARTITION_PAGE,
roROFormatPartitionEntries
},
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
{
CHECK_FILE_SYSTEM_PAGE,
roROCheckFSEntries
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{
DELETE_PARTITION_PAGE,
roRODeletePartitionEntries
},
{
INSTALL_DIRECTORY_PAGE,
roROInstallDirectoryEntries
},
{
PREPARE_COPY_PAGE,
roROPrepareCopyEntries
},
{
FILE_COPY_PAGE,
roROFileCopyEntries
},
{
KEYBOARD_SETTINGS_PAGE,
roROKeyboardSettingsEntries
},
{
BOOT_LOADER_PAGE,
roROBootLoaderEntries
},
{
LAYOUT_SETTINGS_PAGE,
roROLayoutSettingsEntries
},
{
QUIT_PAGE,
roROQuitPageEntries
},
{
SUCCESS_PAGE,
roROSuccessPageEntries
},
[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,
roROBootLoaderInstallPageEntries
},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{
BOOT_LOADER_FLOPPY_PAGE,
roROBootPageEntries
},
{
REGISTRY_PAGE,
roRORegistryEntries
},
{
-1,
NULL
}
};
MUI_STRING roROStrings[] =
{
{STRING_PLEASEWAIT,
[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
" A\272tepta\376i..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_INSTALLCREATEPARTITION,
[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
" ENTER = Instalare P/E = Creare parti\376ie Primar\343/Extins\343 F3 = Ie\272ire"},
[USETUP] - Add status text for logical partition entries in the partition list. - Add logical partition creation page dummy. svn path=/trunk/; revision=63570
2014-06-08 19:05:03 +00:00
{STRING_INSTALLCREATELOGICAL,
[USETUP][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
" ENTER = Instalare L = Creare parti\376ie Logic\343 F3 = Ie\272ire"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_INSTALLDELETEPARTITION,
[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
" ENTER = Instalare D = \252tergere parti\376ie F3 = Ie\272ire"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_DELETEPARTITION,
[USETUP][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 = \252tergere parti\376ie F3 = Ie\272ire"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_PARTITIONSIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"M\343rimea noii parti\376ii:"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{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
"A\376i ales crearea unei parti\376ii primare pe"},
[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
"A\376i ales crearea unei parti\376ii extinse pe"},
[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
"A\376i ales crearea unei parti\376ii logice pe"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Introduce\376i m\343rimea noii parti\376ii \356n megaocte\376i."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_CREATEPARTITION,
[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
" ENTER = Creare parti\376ie ESC = Anulare F3 = Ie\272ire"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_PARTFORMAT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Aceast\343 parti\376ie urmeaz\343 s\343 fie formatat\343."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_NONFORMATTEDPART,
[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
"Alege\376i s\343 instala\376i ReactOS pe parti\376ie nou\343 sau neformatat\343."},
[USETUP] - Implement mandatory filesystem selection, formatting and filesystem checks for all new partitons. - Implement optional filesystem selection, formatting and filesystem checks for formatted boot and install partitions. - Enable installing ReactOS on primary partitions other than the first one. Usetup will install Freeloader on the first (or active) partition (aka boot partition) and install ReactOS on the chosen partition (aka install partition). svn path=/trunk/; revision=68112
2015-06-12 21:51:57 +00:00
{STRING_NONFORMATTEDSYSTEMPART,
[USETUP][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
"Parti\376ia de sistem \356nc\343 nu a fost formatat\343."},
[USETUP] - Implement mandatory filesystem selection, formatting and filesystem checks for all new partitons. - Implement optional filesystem selection, formatting and filesystem checks for formatted boot and install partitions. - Enable installing ReactOS on primary partitions other than the first one. Usetup will install Freeloader on the first (or active) partition (aka boot partition) and install ReactOS on the chosen partition (aka install partition). svn path=/trunk/; revision=68112
2015-06-12 21:51:57 +00:00
{STRING_NONFORMATTEDOTHERPART,
[USETUP][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
"Noua parti\376ie \356nc\343 nu a fost formatat\343."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_INSTALLONPART,
[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 va fi instalat pe parti\376ia"},
[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,
"ENTER = Continuare"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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 = Ie\272ire ENTER = Continuare"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_REBOOTCOMPUTER,
"ENTER = Repornire calculator"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_DELETING,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
" Copiere fi\272ier: %S"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_MOVING,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
" Mutare fi\272ier: %S to: %S"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_RENAMING,
[TRANSLATION] Update the existing romanian resources This includes both newly added and previously left untranslated strings.
2019-01-27 18:47:13 +00:00
" Redenumire fi\272ier: %S to: %S"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_COPYING,
[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
" Fi\272ierul curent: %S"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_SETUPCOPYINGFILES,
[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
"Fi\272iere \356n curs de copiere..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Registru \356n curs de actualizare..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_IMPORTFILE,
[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
" \316n curs de importare din %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
" Registru de configura\376ie grafic\343 \356n actualizare..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Particularit\343\376i locale \356n actualizare..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Configura\376ie de tastatur\343 \356n actualizare..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Date de paginare \356n curs de adaugare \356n registru..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_DONE,
[TRANSLATIONS] * Massive update of Romanian resources. Brought to you by Ștefan Fulea. CORE-7778 #resolve #comment Committed in r61740. Thanks ! svn path=/trunk/; revision=61740
2014-01-20 19:42:49 +00:00
" Terminat!"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_REBOOTCOMPUTER2,
" ENTER = Repornire calculator"},
[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
" Calculatorul va reporni \356n %li secunde... "},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_CONSOLEFAIL1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"E\272ec la deschiderea consolei\r\n\r\n"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_CONSOLEFAIL2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Cea mai frecvent\343 cauz\343 pentru asta este utilizarea unei tastaturi USB\r\n"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Tastaturile USB nu sunt \356nc\343 toate acceptate\r\n"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_FORMATTINGDISK,
[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
"Disc \356n curs de formatare..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Disc \356n curs de verificare..."},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Formateaz\343 parti\376ia ca sistem de fi\272iere %S (formatare rapid\343) "},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" Formateaz\343 parti\376ia ca sistem de fi\272iere %S "},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
" P\343streaz\343 sistemul de fi\272iere actual (f\343r\343 schimb\343ri) "},
[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
"de pe %s."},
{STRING_PARTTYPE,
"Tip 0x%02x"},
{STRING_HDDINFO_1,
// "Discul %lu (%I64u %s), Port=%hu, Magistrala=%hu, Id=%hu (%wZ) [%s]"
"%I64u %s Discul %lu (Port=%hu, Magistrala=%hu, Id=%hu) de tip %wZ [%s]"},
{STRING_HDDINFO_2,
// "Discul %lu (%I64u %s), Port=%hu, Magistrala=%hu, Id=%hu [%s]"
"%I64u %s Discul %lu (Port=%hu, Magistrala=%hu, Id=%hu) [%s]"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"O nou\343 parti\376ie a fost creat\343 \356n"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Spa\376iu neparti\376ionat"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_MAXSIZE,
[TRANSLATION] - Romanian translation update (bug no. 6704) by Stefan Fulea; - Lithuanian UTF-8 translation fixes (bug no. 6716) by Edijs Kolesnikovics; - sysdm translation update by myself; svn path=/trunk/; revision=54583
2011-12-04 14:53:17 +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
"Parti\376ie extins\343"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +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
"Part. nou\343 (neformatat\343)"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_FORMATUNUSED,
"Nefolosit"},
{STRING_FORMATUNKNOWN,
"Necunoscut"},
{STRING_KB,
[TRANSLATION] - Romanian translation update (bug no. 6704) by Stefan Fulea; - Lithuanian UTF-8 translation fixes (bug no. 6716) by Edijs Kolesnikovics; - sysdm translation update by myself; svn path=/trunk/; revision=54583
2011-12-04 14:53:17 +00:00
"ko"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_MB,
[TRANSLATION] - Romanian translation update (bug no. 6704) by Stefan Fulea; - Lithuanian UTF-8 translation fixes (bug no. 6716) by Edijs Kolesnikovics; - sysdm translation update by myself; svn path=/trunk/; revision=54583
2011-12-04 14:53:17 +00:00
"Mo"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_GB,
[TRANSLATION] - Romanian translation update (bug no. 6704) by Stefan Fulea; - Lithuanian UTF-8 translation fixes (bug no. 6716) by Edijs Kolesnikovics; - sysdm translation update by myself; svn path=/trunk/; revision=54583
2011-12-04 14:53:17 +00:00
"Go"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{STRING_ADDKBLAYOUTS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Ad\343ugare configura\376ii de tastatur\343"},
[TRANSLATION] - Romanian syssetup and usetup translation by Stefan Fulea <fulea.stefan> at <gmail.com>; - Fix ipconfig build under MSVC, use "" instead of \" as escape character; svn path=/trunk/; revision=53539
2011-09-03 01:09:42 +00:00
{0, 0}
};
Reference in a new issue Copy permalink