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

2354 lines
80 KiB
C
Raw Normal View History

[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
// This file is converted by code7bit.
// code7bit: https://github.com/katahiromz/code7bit
// To revert conversion, please execute "code7bit -r <file>".
- Move from using include guards to pragma once. - Whilst this is non-standard and potentially makes the code less portable, it's supported by both gcc and msvc and should bringg increased compilation speed due to its optimized behaviour (doesn't need to invoke the preprocessor) - Patch by Amine Khaldi [amine.khaldi@reactos.org] svn path=/trunk/; revision=45685
2010-02-26 11:43:19 +00:00
#pragma once
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 bgBGSetupInitPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\214\256\253\357 \250\247\347\240\252\240\251\342\245 \244\256\252\240\342\256 \341\245 \257\256\244\243\256\342\242\357 \250\255\341\342\240\253\240\346\250\357\342\240 \255\240 ReactOS",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER,
TEXT_ID_STATIC
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
},
{
0,
21,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250 \256\342\252\340\250\242\240 \242\240\350\250\342\245 \343\341\342\340\256\251\341\342\242\240...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\214\256\253\357 \250\247\347\240\252\240\251\342\245...",
[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
}
};
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
static MUI_ENTRY bgBGLanguagePageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\210\247\241\256\340 \255\240 \245\247\250\252",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
10,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \210\247\241\245\340\245\342\245 \245\247\250\252, \252\256\251\342\256 \244\240 \250\247\257\256\253\242\240\342\245 \257\340\250 \250\255\341\342\240\253\250\340\240\255\245\342\256.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \255\240\342\250\341\255\245\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
13,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \212\340\240\251\255\240\342\240 \250\255\341\342\240\253\240\346\250\357 \351\245 \241\352\244\245 \255\240 \250\247\241\340\240\255\250\357 \256\342 \242\240\341 \245\247\250\252.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGWelcomePageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\204\256\241\340\245 \244\256\350\253\250 \242 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
11,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\242\352\340\350\242\240 \341\245 \247\240\257\250\341 \255\240 \256\257\245\340\240\346\250\256\255\255\240\342\240 \341\250\341\342\245\254\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\242 \254\256\254\245\255\342\240 \342\245\347\245 \255\240\341\342\340\256\251\252\240\342\240 \255\240 \341\250\341\342\245\254\240\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
15,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ENTER \244\240 \250\255\341\342\240\253\250\340\240\342\245 \250\253\250 \256\241\255\256\242\250\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
17,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 R \247\240 \244\240 \257\256\257\340\240\242\250\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
19,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 L, \247\240 \244\240 \256\342\242\256\340\250\342\245 \253\250\346\245\255\247\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +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
{
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
8,
20,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \343\341\253\256\242\250\357 \247\240 \257\256\253\247\242\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
22,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 F3 \247\240 \250\247\345\256\244 \256\342 \250\255\341\342\240\253\240\346\250\357\342\240 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
24,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\207\240 \257\256\242\245\347\245 \250\255\344\256\340\254\240\346\250\357 \256\342\255\256\341\255\256 ReactOS \257\256\341\245\342\245\342\245:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
25,
[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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 R = \217\256\257\340\240\242\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGIntroPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\221\342\240\342\343\341 \255\240 \242\245\340\341\250\357\342\240 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ReactOS \245 \242 \245\342\240\257 \240\253\344\240 \250 \255\245 \242\341\250\347\252\250 \344\343\255\252\346\250\250 \341\240 \255\240\253\250\346\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\242 \254\256\254\245\255\342\240 \245 \242 \257\340\256\346\245\341 \255\240 \250\255\342\245\255\247\250\242\255\240 \340\240\247\340\240\241\256\342\252\240. \217\340\245\257\256\340\352\347\242\240 \341\245 \244\240 \341\245 ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
13,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250\247\257\256\253\247\242\240 \341\240\254\256 \247\240 \342\245\341\342\242\240\255\245, \240 \255\245 \252\240\342\256 \256\257\245\340\240\346\250\256\255\255\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
14,
"\341\250\341\342\245\254\240 \247\240 \245\246\245\244\255\245\242\255\240 \343\257\256\342\340\245\241\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
},
{
6,
16,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\240\257\340\240\242\245\342\245 \340\245\247\245\340\242\255\256 \252\256\257\250\245 \255\240 \244\240\255\255\250\342\245 \341\250 \250\253\250 \342\245\341\342\242\240\251\342\245 \255\240 \244\340\343\243 \252\256\254\257\356\342\352\340",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
17,
"\247\240 \244\240 \250\247\257\256\253\247\242\240\342\245 ReactOS \255\240 \344\250\247\250\347\245\341\252\250 \252\256\254\257\356\342\352\340.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
20,
"\x07 \215\240\342\250\341\255\245\342\245 ENTER \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245 \250\255\341\342\240\253\240\346\250\357\342\240 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
22,
"\x07 \215\240\342\250\341\255\245\342\245 F3 \247\240 \244\240 \257\340\245\252\341\352\255\245\342\245 \250\255\341\342\240\253\240\346\250\357\342\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGLicensePageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
6,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\213\250\346\245\255\247:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ReactOS \245 \253\250\346\245\255\247\250\340\240\255\240 \257\256\244 \253\250\346\245\255\247\240 GNU GPL",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\341 \347\240\341\342\250, \341\352\244\352\340\246\240\351\250 \252\256\244 \256\342 \244\340\343\243\250 \341\352\242\254\245\341\342\250\254\250 \253\250\346\245\255\247\250 \252\240\342\256",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"X11, BSD \250\253\250 GNU LGPL.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
11,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\221\253\245\244\256\242\240\342\245\253\255\256 \242\341\357\252\240 \257\256\257\340\240\242\252\240, \252\256\357\342\256 \245 \347\240\341\342 \256\342",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ReactOS, \341\245 \257\343\241\253\250\252\343\242\240 \257\256\244 GNU GPL \253\250\346\245\255\247.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
15,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\222\256\247\250 \341\256\344\342\343\245\340 \341\245 \257\340\245\244\253\240\243\240 \201\205\207 \203\200\220\200\215\226\210\237 \250\253\250 \256\243\340\240\255\250\347\245\255\250\357 \247\240 \343\257\256\342\340\245\241\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
16,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\256\341\242\245\255 \257\340\250\253\256\246\250\254\250\342\245 \254\245\341\342\255\250 \250\253\250 \254\245\246\244\343\255\240\340\256\244\255\250 \247\240\252\256\255\250. \213\250\346\245\255\247\250\340\240\255\245\342\256 \255\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
17,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ReactOS \257\256\252\340\250\242\240 \341\240\254\256 \340\240\247\257\340\256\341\342\340\240\255\245\255\250\245\342\256 \255\240 \342\340\245\342\250 \341\342\340\240\255\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
18,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\200\252\256 \257\256\340\240\244\250 \255\357\252\240\252\242\240 \257\340\250\347\250\255\240, \247\240\245\244\255\256 \341 ReactOS \255\245 \341\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\257\256\253\343\347\250\253\250 \252\256\257\250\245 \255\240 GNU General Public License, \257\256\341\245\342\245\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
20,
"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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
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
"\203\240\340\240\255\346\250\357:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
24,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\222\256\242\240 \245 \341\242\256\241\256\244\245\255 \341\256\344\342\343\245\340: \242\250\246\342\245 \250\247\345\256\244\255\250\357 \252\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
25,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\247\240 \343\341\253\256\242\250\357\342\240 \255\240 \340\240\247\257\340\256\341\342\340\240\255\245\255\250\245.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
26,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\222\343\252 \255\357\254\240 \243\240\340\240\255\346\250\357 \247\240 \342\352\340\243\256\242\341\252\256 \257\340\250\253\256\246\245\255\250\245 \250\253\250",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
8,
27,
"\257\340\250\243\256\244\255\256\341\342 \247\240 \252\256\255\252\340\245\342\255\256 \257\340\250\253\256\246\245\255\250\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \215\240\247\240\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGDevicePageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\221\257\250\341\352\252\352\342 \257\256-\244\256\253\343 \257\256\252\240\247\242\240 \342\245\252\343\351\250\342\245 \255\240\341\342\340\256\251\252\250 \255\240 \343\341\342\340\256\251\341\342\242\240\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \212\256\254\257\356\342\352\340:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
4,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \220\245\247\256\253\356\346\250\357:",
- Allow multiple combination of style flags for usetup translations - Added right & center text align , no more space counting :). All localization can now share X,Y cordinates Note: only the en-US localization currently takes advantage of it , other localizations should be updated svn path=/trunk/; revision=32722
2008-03-19 04:43:40 +00:00
TEXT_STYLE_NORMAL,
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
3,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
13,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \212\253\240\242\250\240\342\343\340\240:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
3,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\212\253\240\242\250\240\342\343\340\255\240 \257\256\244\340\245\244\241\240:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
3,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \217\340\250\245\254\240\255\245:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
25,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
16, "\217\340\250\245\254\240\255\245 \255\240 \255\240\341\342\340\256\251\252\250\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\207\240 \244\240 \257\340\256\254\245\255\250\342\245 \255\240\341\342\340\256\251\252\250\342\245 \255\240 \256\241\256\340\343\244\242\240\255\245\342\256, \250\247\257\256\253\247\242\240\251\342\245 \341\342\340\245\253\252\250\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\215\200\203\216\220\205 \250 \215\200\204\216\213\223. \221\253\245\244 \342\256\242\240 \255\240\342\250\341\255\245\342\245 ENTER, \247\240 \244\240 \250\247\241\245\340\245\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
21,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\244\340\343\243\250 \255\240\341\342\340\256\251\252\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\212\256\243\240\342\256 \255\240\257\340\240\242\250\342\245 \242\341\250\347\252\250 \255\240\341\342\340\256\251\252\250, \250\247\241\245\340\245\342\245 '\217\340\250\245\254\240\255\245 \255\240 \255\240\341\342\340\256\251\252\250\342\245'",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\250 \255\240\342\250\341\255\245\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGRepairPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\240\341\342\340\256\251\252\250\342\245 \255\240 ReactOS \341\240 \242\341\245 \256\351\245 \242 \340\240\255\245\255 \245\342\240\257 \255\240 \340\240\247\340\240\241\256\342\252\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
9,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250 \255\357\254\240\342 \242\341\250\347\252\250 \256\257\346\250\250 \247\240 \255\240\341\342\340\256\251\252\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\216\257\346\250\357\342\240 \247\240 \257\256\257\340\240\242\252\240 \255\240 ReactOS \242\341\245 \256\351\245 \255\245 \245 \243\256\342\256\242\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \255\240\342\250\341\255\245\342\245 U \247\240 \256\241\255\256\242\357\242\240\255\245 \255\240 \256\257\245\340\240\346\250\256\255\255\240\342\240 \341\250\341\342\245\254\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
17,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 R \247\240 \242\352\247\341\342\240\255\256\242\357\242\240\255\245 (\341\342\240\340\342\250\340\240 \252\256\255\247\256\253\240).",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \255\240\342\341\250\255\245\342\245 ESC \247\240 \242\340\352\351\240\255\245 \252\352\254 \243\253\240\242\255\240\342\240 \341\342\340\240\255\250\346\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
21,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ENTER \247\240 \340\245\341\342\240\340\342\250\340\240\255\245 \255\240 \252\256\254\257\356\342\352\340\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ESC = \203\253\240\242\255\240 \341\342\340\240\255\250\346\240 ENTER = \220\245\341\342\240\340\342\250\340\240\255\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 bgBGUpgradePageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\216\241\255\256\242\357\242\240\255\245\342\256 \255\240 ReactOS \254\256\246\245 \244\240 \255\240\244\341\342\340\256\250 \245\244\255\240 \256\342 \341\253\245\244\255\250\342\245 \250\255\341\342\240\253\346\250\250",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250\247\241\340\256\245\255\250 \257\256-\255\240\244\256\253\343, \250\253\250 \240\252\256 ReactOS \245 \257\256\242\340\245\244\245\255\240, \250\255\341\342\240\253\240\346\250\357\342\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\254\256\246\245 \244\240 \357 \257\256\257\340\240\242\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\224\343\255\252\346\250\250\342\245 \247\240 \257\256\257\340\240\242\252\240 \255\245 \341\240 \340\240\247\340\240\241\256\342\245\255\250 \256\351\245.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 \215\200\203\216\220\205 \250\253\250 \215\200\204\216\213\223 \247\240 \244\240 \250\247\241\245\340\245\342\245 \256\257\245\340\240\346\250\256\255\255\240\342\240 \341\250\341\342\245\254\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 U \247\240 \256\241\255\256\242\357\242\240\255\245 \255\240 \250\247\241\340\240\255\240\342\240 \256\257\245\340\240\346\250\256\255\255\240 \341\250\341\342\245\254\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ESC \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245 \341 \255\256\242\240 \250\255\341\342\240\253\240\346\250\357.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 F3 \247\240 \244\240 \250\247\253\245\247\245\342\245 \241\245\247 \244\240 \250\255\341\342\240\253\250\340\240\342\245 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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"U = \216\241\255\256\242\250 ESC = \215\245 \256\241\255\256\242\357\242\240\251 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
}
};
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
static MUI_ENTRY bgBGComputerPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\220\245\350\250\253\250 \341\342\245 \244\240 \341\254\245\255\250\342\245 \342\250\257\240 \255\240 \252\256\254\257\356\342\352\340\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
10,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \210\247\241\245\340\245\342\245 \342\250\257\240 \255\240 \252\256\254\257\356\342\352\340\240 \341\352\341 \341\342\340\245\253\252\250\342\245 \255\240\243\256\340\245 \250 \255\240\244\256\253\343 \250 ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \255\240\342\250\341\255\245\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \215\240\342\250\341\255\245\342\245 ESC, \247\240 \244\240 \341\245 \242\352\340\255\245\342\245 \252\352\254 \257\340\245\244\345\256\244\255\240\342\240 \341\342\340\240\255\250\346\240, \241\245\247 \244\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
14,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \341\254\245\255\357\342\245 \342\250\257\240 \255\240 \252\256\254\257\356\342\352\340\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 ESC = \216\342\252\240\247 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGFlushPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
6,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \257\340\256\242\245\340\357\242\240, \244\240\253\250 \242\341\250\347\252\250 \244\240\255\255\250 \341\240 \247\240\257\250\341\240\255\250 \255\240 \244\250\341\252\240 \242\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\222\256\242\240 \351\245 \256\342\255\245\254\245 \254\250\255\343\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
9,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\212\256\254\257\356\342\352\340\352\342 \242\250 \351\245 \341\245 \340\245\341\342\240\340\342\250\340\240 \341\240\254, \252\256\243\240\342\256 \257\340\250\252\253\356\347\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \210\247\347\250\341\342\242\240\255\245 \255\240 \252\245\350\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGQuitPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
6,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\250\340\240\255\245\342\256 \255\240 \220\245\240\252\342\216\221 \255\245 \245 \257\340\250\252\253\356\347\250\253\256.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\210\247\242\240\244\245\342\245 \244\250\341\252\245\342\240\342\240 \256\342 \343\341\342\340\256\251\341\342\242\256 \200: \250",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
9,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\242\341\250\347\252\250 \255\256\341\250\342\245\253\250 \256\342 CD \250 DVD \343\341\342\340\256\251\341\342\242\240\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
11,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\240\342\250\341\255\245\342\245 ENTER, \247\240 \244\240 \340\245\341\342\240\340\342\250\340\240\342\245 \252\256\254\257\356\342\352\340\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \214\256\253\357 \250\247\347\240\252\240\251\342\245...",
- Allow multiple combination of style flags for usetup translations - Added right & center text align , no more space counting :). All localization can now share X,Y cordinates Note: only the en-US localization currently takes advantage of it , other localizations should be updated svn path=/trunk/; revision=32722
2008-03-19 04:43:40 +00:00
TEXT_TYPE_STATUS,
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGDisplayPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\220\245\351\250\253\250 \341\342\245 \244\240 \341\254\245\255\250\342\245 \340\245\247\256\253\356\346\250\357\342\240 \255\240 \245\252\340\240\255\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
10,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \210\247\241\245\340\245\342\245 \340\245\247\256\253\356\346\250\357\342\240 \341\352\341 \341\342\340\245\253\252\250\342\245 \255\240\243\256\340\245 \250 \255\240\244\256\253\343 \250 ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \255\240\342\250\341\255\245\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \215\240\342\250\341\255\245\342\245 ESC, \247\240 \244\240 \341\245 \242\352\340\255\245\342\245 \252\352\254 \257\340\245\244\345\256\244\255\240\342\240 \341\342\340\240\255\250\346\240, \241\245\247 \244\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
14,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \341\254\245\255\357\342\245 \340\245\247\256\253\356\346\250\357\342\240 \255\240 \245\252\340\240\255\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 ESC = \216\342\252\240\247 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGSuccessPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
6,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\216\341\255\256\242\255\240\342\240 \341\250\341\342\245\254\240 \255\240 ReactOS \245 \250\255\341\342\240\253\250\340\240\255\240 \343\341\257\245\350\255\256.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\210\247\242\240\244\245\342\245 \244\250\341\252\245\342\240\342\240 \256\342 \343\341\342\340\256\251\341\342\242\256 \200: \250",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
9,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\242\341\250\347\252\250 \255\256\341\250\342\245\253\250 \256\342 \256\257\342\250\347\255\250\342\245 \343\341\342\340\256\251\341\342\242\240 (CD/DVD)",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
10,
11,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\240\342\250\341\255\245\342\245 ENTER, \247\240 \244\240 \340\245\341\342\240\340\342\250\340\240\342\245 \252\256\254\257\356\342\352\340\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \220\245\341\342\240\340\342\250\340\240\255\245 \255\240 \252\256\254\257\356\342\352\340\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGSelectPartitionEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\221\257\250\341\352\252\352\342 \257\256-\244\256\253\343 \341\352\244\352\340\246\240 \341\352\351\245\341\342\242\343\242\240\351\250\342\245 \244\357\253\256\242\245 \250 \257\340\240\247\255\256\342\256",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\254\357\341\342\256 \247\240 \255\256\242\250 \244\357\253\256\242\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \210\247\257\256\253\247\242\240\251\342\245 \341\342\340\245\253\252\250\342\245 \247\240 \250\247\241\256\340 \256\342 \341\257\250\341\352\252\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
13,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ENTER \247\240 \250\255\341\342\240\253\250\340\240\255\245 \255\240 \220\245\240\252\342\216\221 \255\240 \250\247\241\340\240\255\250\357 \244\357\253.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
15,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 C \247\240 \341\352\247\244\240\242\240\255\245 \255\240 \243\253\240\242\245\255/\253\256\243\250\347\245\341\252\250 \244\357\253.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
17,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 E \247\240 \341\352\247\244\240\242\240\255\245 \255\240 \340\240\247\350\250\340\245\255 \244\357\253.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 \215\240\342\250\341\255\245\342\245 D \247\240 \250\247\342\340\250\242\240\255\245 \255\240 \341\352\351\245\341\342\242\343\242\240\351 \244\357\253.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \217\256\347\240\252\240\251\342\245...", /* <20><><EFBFBD><EFBFBD><EFBFBD> <20><> <20><> <20><> <20>ॢ<EFBFBD><E0A5A2><EFBFBD><EFBFBD>, <20><><EFBFBD><EFBFBD><EFBFBD><EFBFBD> ᯨ<><E1AFA8><EFBFBD><EFBFBD><EFBFBD> <20> <20>﫮<EFBFBD><EFABAE><EFBFBD><EFBFBD> <20><> <20><> ࠧ<><E0A0A7><EFBFBD><EFBFBD><EFBFBD> */
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 bgBGChangeSystemPartition[] =
{
{
4,
3,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ReactOS " KERNEL_VERSION_STR " \210\255\341\342\240\253\240\346\250\357 ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\222\245\252\343\350\250\357\342 \341\250\341\342\245\254\245\255 \244\357\253 \255\240 \242\240\350\250\357 \252\256\254\257\356\342\352\340",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\255\240 \341\250\341\342\245\254\255\250\357 \244\250\341\252",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250\247\257\256\253\247\242\240 \344\256\340\254\240\342 \255\245\257\256\244\244\352\340\246\240\255 \256\342 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\207\240 \244\240 \250\255\341\342\240\253\250\340\240\342\245 \343\341\257\245\350\255\256 ReactOS, \342\340\357\241\242\240 \244\240 \257\340\256\254\245\255\250\342\245 \255\240\341\342\340\256\251\252\250\342\245 \247\240 \250\255\341\342\240\253\240\346\250\357",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250 \244\240 \341\254\245\255\250\342\245 \342\245\252\343\351\250\357 \341\250\341\342\245\254\245\255 \244\357\253 \341 \255\256\242.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\256\340\352\342 \247\240 \255\256\242 \341\250\341\342\245\254\245\255 \244\357\253 \245: ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \207\240 \244\240 \257\256\342\242\352\340\244\250\342\245 \250\247\241\256\340\240 \341\250 \255\240\342\250\341\255\245\342\245 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \207\240 \244\240 \257\340\256\254\245\255\250\342\245 \341\250\341\342\245\254\255\250\357 \244\357\253 \255\240\342\250\341\255\245\342\245 ESC \247\240 \244\240 \341\245 \242\352\340\255\245\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \255\240 \341\257\250\341\352\252\240 \247\240 \250\247\241\256\340 \255\240 \244\357\253\256\242\245, \252\352\244\245\342\256 \254\256\246\245\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \255\256\242 \244\357\253",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \255\240 \341\250\341\342\245\254\255\250\357 \244\250\341\252.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\202 \341\253\343\347\240\251, \347\245 \250\254\240 \244\340\343\243\250 \256\257\245\340\240\346\250\256\255\255\250 \341\250\341\342\245\254\250 \252\256\250\342\256 \247\240\242\250\341\357\342 \256\342",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\341\250\341\342\245\254\255\250\357 \244\357\253, \254\256\246\245 \244\240 \341\245 \255\240\253\256\246\250 \244\240 \243\250 \257\340\245\252\256\255\344\250\243\343\340\250\340\240\342\245 \247\240 \255\256\242\250\357",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\341\250\341\342\245\254\245\255 \244\357\253, \250\253\250 \254\256\246\245 \244\240 \341\245 \255\240\253\256\246\250 \244\240 \257\340\256\254\245\255\250\342\245 \341\250\341\342\245\254\255\250\357 \244\357\253 \256\241\340\240\342\255\256",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\252\352\254 \256\340\250\243\250\255\240\253\240 \341\253\245\244 \257\340\250\252\253\356\347\242\240\255\245 \255\240 \250\255\341\342\240\253\240\346\250\357\342\240 \255\240 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \217\340\256\244\352\253\246\250 ESC = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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 bgBGConfirmDeleteSystemPartitionEntries[] =
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] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\340\240\253\250 \341\342\245 \244\240 \250\247\342\340\250\245\342\245 \341\250\341\342\245\254\255\250\357 \244\357\253.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\221\250\341\342\245\254\255\250\342\245 \244\357\253\256\242\245 \254\256\243\240\342 \244\240 \341\352\244\352\340\246\240\342, \257\340\256\243\340\240\254\250 \247\240 \244\250\240\243\255\256\341\342\250\252\240, \257\340\256\243\340\240\254\250 \247\240 \345\240\340\244\343\245\340\255\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\252\256\255\344\250\243\343\340\240\346\250\357, \257\340\256\243\340\240\254\250 \247\240 \341\342\240\340\342\250\340\240\255\245 \255\240 \256\257\245\340\240\346\250\256\255\255\240\342\240 \341\250\341\342\245\254\240 (\252\240\342\256 ReactOS) \250\253\250 \244\340\343\243\250",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\257\340\256\243\340\240\254\250 \257\340\245\244\256\341\342\240\242\245\255\250 \256\342 \257\340\256\250\247\242\256\244\250\342\245\253\357 \255\240 \345\240\340\244\343\245\340\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\342\340\250\251\342\245 \341\250\341\342\245\254\255\250\357 \244\357\253 \341\240\254\256 \240\252\256 \341\342\245 \341\250\243\343\340\245\255, \347\245 \255\357\254\240 \342\240\252\250\242\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\257\340\256\243\340\240\254\250 \250\253\250 \244\357\253\256\242\245, \250\253\250 \341\342\245 \341\250\243\343\340\255\250, \347\245 \250\341\252\240\342\245 \244\240 \243\250 \250\247\342\340\250\245\342\245.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\212\240\342\256 \250\247\342\340\250\245\342\245 \244\357\253\240, \254\256\246\245 \244\240 \255\245 \343\341\257\245\245\342\245 \244\240 \341\342\240\340\342\250\340\240\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\252\256\254\257\356\342\352\340 \256\342 \342\242\352\340\244\250\357 \244\250\341\252, \244\256\252\240\342\256 \247\240\242\352\340\350\250\342\245 \255\240\341\342\340\256\251\252\240\342\240 \255\240 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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ENTER \244\240 \250\247\342\340\250\245\342\245 \341\250\341\342\245\254\255\250\357 \244\357\253. \231\245 \241\352\244\245\342\245 \257\256\257\250\342\240\255\250",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \247\240 \244\240 \257\256\342\242\352\340\244\250\342\245 \250\247\342\340\250\242\240\255\245\342\256 \255\240 \244\357\253\240 \256\342\255\256\242\256 \257\256-\252\352\341\255\256.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ESC \247\240 \242\340\352\351\240\255\245 \255\240 \257\340\245\244\250\350\255\240\342\240 \341\342\340\240\255\250\346\240. \217\240\340\342\250\350\352\255\250\342\245 \255\357\254\240 \244\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \241\352\244\240\342 \250\247\342\340\250\342\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER=\217\340\256\244\352\253\246\250 ESC=\210\247\342\340\250\251",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
}
};
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
static MUI_ENTRY bgBGFormatPartitionEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\224\256\340\254\240\342\250\340\240\255\245 \255\240 \244\357\253",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
2023-10-25 20:19:39 +00:00
16,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\204\357\253\352\342 \351\245 \241\352\244\245 \344\256\340\254\240\342\250\340\240\255. \215\240\342\250\341\255\245\342\245 ENTER \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_FORMAT_PROMPT
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 bgBGCheckFSEntries[] =
{
{
4,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
3,
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 ReactOS " KERNEL_VERSION_STR " ",
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\242\352\340\350\242\240 \341\245 \257\340\256\242\245\340\252\240 \255\240 \250\247\241\340\240\255\250\357 \244\357\253.",
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\214\256\253\357 \257\256\347\240\252\240\251\342\245...",
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
static MUI_ENTRY bgBGInstallDirectoryEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\224\240\251\253\256\242\245\342\245 \255\240 ReactOS \351\245 \241\352\244\240\342 \252\256\257\250\340\240\255\250 \255\240 \250\247\241\340\240\255\250\357 \244\357\253. \210\247\241\245\340\245\342\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
9,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\257\240\257\252\240, \242 \252\256\357\342\256 \244\240 \241\352\244\245 \250\255\341\342\240\253\250\340\240\255 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
14,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\207\240 \257\340\256\254\357\255\240 \255\240 \257\340\245\244\253\256\246\245\255\240\342\240 \257\240\257\252\240 \255\240\342\250\341\255\245\342\245 BACKSPACE, \247\240 \244\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
15,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250\247\342\340\250\245\342\245 \342\245\252\343\351\240\342\240 \250 \342\256\243\240\242\240 \255\240\257\250\350\245\342\245 \255\256\242 \257\352\342, \242 \252\256\357\342\256 \244\240 \241\352\244\245",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
16,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\250\255\341\342\240\253\250\340\240\255 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGFileCopyEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
11,
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\347\240\252\240\251\342\245 \244\240 \257\340\250\252\253\356\347\250 \252\256\257\250\340\240\255\245\342\256 \255\240 \344\240\251\253\256\242\245\342\245 \242 \250\247\241\340\240\255\240\342\240 \244\250\340\245\252\342\256\340\250\357.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
30,
13,
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
// "<22><><EFBFBD>࠭<EFBFBD><E0A0AD><EFBFBD> <20><><EFBFBD><EFBFBD><EFBFBD>.",
"",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
20,
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
"\222\256\242\240 \254\256\246\245 \244\240 \256\342\255\245\254\245 \255\357\252\256\253\252\256 \254\250\255\343\342\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \xB3 \214\256\253\357 \250\247\347\240\252\240\251\342\245... ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
static MUI_ENTRY bgBGBootLoaderSelectPageEntries[] =
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
"Please select where Setup should install the bootloader:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
12,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\250\340\240\255\245 \255\240 \247\240\340\245\246\244\240\351\240 \257\340\256\243\340\240\254\240 \255\240 \342\242\352\340\244\250\357 \244\250\341\252 (MBR \250 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
13,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\250\340\240\255\245 \255\240 \247\240\340\245\246\244\240\351\240 \257\340\256\243\340\240\254\240 \255\240 \342\242\352\340\244\250\357 \244\250\341\252 (\341\240\254\256 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
14,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\250\340\240\255\245 \255\240 \247\240\340\245\246\244\240\351\240 \257\340\256\243\340\240\254\240 \255\240 \244\250\341\252\245\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] - Add the option to write only the VBR so FreeLoader can easily be chain loaded by GRUB or another boot loader - Dedicated to James Tabor :) svn path=/trunk/; revision=48703
2010-09-05 17:09:18 +00:00
},
{
8,
15,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\204\240 \255\245 \341\245 \250\255\341\342\240\253\250\340\240 \247\240\340\245\246\244\240\351\240 \257\340\256\243\340\240\254\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 bgBGBootLoaderInstallPageEntries[] =
{
{
4,
3,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ReactOS " KERNEL_VERSION_STR " \210\255\341\342\240\253\240\346\250\357 ",
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
{
6,
8,
"\217\340\256\342\250\347\240 \250\255\341\342\240\253\250\340\240\255\245\342\256 \255\240 \247\240\340\245\246\244\240\351\240\342\240 \257\340\256\243\340\240\254\240.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\250\340\240 \341\245 \247\240\340\245\246\244\240\351\240\342\240 \257\340\256\243\340\240\254\240, \254\256\253\357 \250\247\347\240\252\240\251\342\245...",
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
static MUI_ENTRY bgBGBootLoaderRemovableDiskPageEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 ReactOS " KERNEL_VERSION_STR " ",
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
},
{
6,
8,
"\210\255\341\342\240\253\250\340\240\255\245 \255\240 \247\240\340\245\246\244\240\351\240\342\240 \257\340\256\243\340\240\254\240 (bootloader) \255\240 \244\250\341\252\240 \255\240 \252\256\254\257\356\342\352\340\240 \242\250",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
9,
"\241\245 \255\245\343\341\257\245\350\255\256.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
13,
"\221\253\256\246\245\342\245 \344\256\340\254\240\342\250\340\240\255\240 \244\250\341\252\245\342\240 \242 \343\341\342\340\256\251\341\342\242\256 A:",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
6,
14,
"\250 \255\240\342\250\341\255\245\342\245 ENTER.",
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
},
{
0,
0,
" ENTER = \217\340\256\244\352\253\246\250 F3 = \210\247\345\256\244",
TEXT_TYPE_STATUS,
TEXT_ID_STATIC
},
{
0,
0,
NULL,
0
}
};
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
static MUI_ENTRY bgBGKeyboardSettingsEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\341\252\240\342\245 \244\240 \341\254\245\255\250\342\245 \342\250\257\240 \255\240 \252\253\240\242\250\240\342\343\340\240\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
10,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\x07 \210\247\257\256\253\247\242\240\251\342\245 \341\342\340\245\253\252\250\342\245, \247\240 \244\240 \250\247\241\245\340\245\342\245 \342\250\257\240 \255\240 \252\253\240\242\250\240\342\343\340\240\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \255\240\342\250\341\255\245\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \215\240\342\250\341\255\245\342\245 ESC, \247\240 \244\240 \341\245 \242\352\340\255\245\342\245 \252\352\254 \257\340\245\244\345\256\244\255\240\342\240 \341\342\340\240\255\250\346\240, \241\245\247 \244\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
8,
14,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \341\254\245\255\357\342\245 \342\250\257\240 \255\240 \252\253\240\242\250\240\342\343\340\240\342\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 ESC = \216\342\252\240\247 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGLayoutSettingsEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\245\340\245\342\245 \252\253\240\242\250\240\342\343\340\255\240 \257\256\244\340\245\244\241\240 \257\256 \257\256\244\340\240\247\241\250\340\240\255\245.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \210\247\257\256\253\247\242\240\251\342\245 \341\342\340\245\253\252\250\342\245, \247\240 \244\240 \250\247\241\245\340\245\342\245 \246\245\253\240\255\240\342\240 \252\253\240\242\250\240\342\343\340\255\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \257\256\244\340\245\244\241\240 \250 \257\256\341\253\245 \255\240\342\250\341\255\245\342\245 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \215\240\342\250\341\255\245\342\245 ESC, \247\240 \244\240 \341\245 \242\352\340\255\245\342\245 \252\352\254 \257\340\245\244\345\256\244\255\240\342\240 \341\342\340\240\255\250\346\240, \241\245\247 \244\240",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" \341\254\245\255\357\342\245 \252\253\240\242\250\240\342\343\340\255\240\342\240 \257\256\244\340\245\244\241\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 ESC = \216\342\252\240\247 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY bgBGPrepareCopyEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
"\212\256\254\257\356\342\352\340\352\342 \341\245 \257\256\244\243\256\342\242\357 \247\240 \247\240\257\250\341 \255\240 \344\240\251\253\256\242\245\342\245 \255\240 \220\245\240\252\342\216\221.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \217\256\244\243\256\342\242\357\255\245 \255\240 \341\257\250\341\352\252\240 \256\342 \344\240\251\253\256\242\245 \247\240 \247\240\257\250\341...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY bgBGSelectFSEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\207\240 \244\240 \250\247\241\245\340\245\342\245 \344\240\251\253\256\242\240 \341\250\341\342\245\254\240 \256\342 \244\256\253\255\250\357 \341\257\250\341\352\252:",
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
0
},
{
8,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 \210\247\241\245\340\245\342\245 \344\240\251\253\256\242\240 \341\250\341\342\245\254\240 \341\352\341 \341\342\340\245\253\252\250\342\245.",
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
0
},
{
8,
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ENTER, \247\240 \244\240 \344\256\340\254\240\342\250\340\240\342\245 \244\357\253\240.",
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
0
},
{
8,
23,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 \215\240\342\250\341\255\245\342\245 ESC, \247\240 \244\240 \250\247\241\245\340\245\342\245 \244\340\343\243 \244\357\253.",
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
0
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \217\340\256\244\352\253\246\250 ESC = \216\342\252\240\247 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGDeletePartitionEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\210\247\241\340\240\253\250 \341\342\245 \244\240 \250\247\342\340\250\245\342\245 \244\357\253",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \215\240\342\250\341\255\245\342\245 L, \247\240 \244\240 \250\247\342\340\250\245\342\245 \244\357\253\240.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\202\215\210\214\200\215\210\205: \202\341\250\347\252\250 \244\240\255\255\250 \255\240 \342\256\247\250 \244\357\253 \351\245 \241\352\244\240\342 \343\255\250\351\256\246\245\255\250!",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 \215\240\342\250\341\255\245\342\245 ESC, \247\240 \244\240 \341\245 \256\342\252\240\246\245\342\245.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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 = \210\247\342\340\250\242\240\255\245 \255\240 \244\357\253\240, ESC = \216\342\252\240\247 F3 = \210\247\345\256\244",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY bgBGRegistryEntries[] =
{
{
4,
3,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" \210\255\341\342\240\253\250\340\240\255\245 \255\240 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
6,
8,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\216\241\255\256\242\357\242\240\255\245 \255\240 \341\250\341\342\245\254\255\250\342\245 \255\240\341\342\340\256\251\252\250.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \221\352\247\244\240\242\240\255\245 \255\240 \340\245\243\250\341\342\340\250\342\245...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
0,
0,
NULL,
0
},
};
MUI_ERROR bgBGErrorEntries[] =
{
[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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\223\341\257\245\350\255\256\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
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ReactOS \255\245 \245 \255\240\257\352\253\255\256 \250\255\341\342\240\253\250\340\240\255 \255\240 \252\256\254\257\356\342\352\340\240\n"
"\242\250. \200\252\256 \341\245\243\240 \257\340\245\252\352\341\255\245\342\245 \250\255\341\342\240\253\240\346\250\357\342\240, \351\245 \342\340\357\241\242\240\n"
"\244\240 \357 \257\343\341\255\245\342\245 \256\342\255\256\242\256, \247\240 \244\240 \250\255\341\342\240\253\250\340\240\342\245 ReactOS.\n"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
"\n"
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \x07 \207\240 \244\240 \257\340\256\244\352\253\246\250 \250\255\341\342\240\253\250\340\240\255\245\342\256, \255\240\342\250\341\255\245\342\245 ENTER.\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \x07 \207\240 \250\247\345\256\244 \255\240\342\250\341\255\245\342\245 F3.",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"F3 = \210\247\345\256\244 ENTER = \217\340\256\244\352\253\246\250"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
{
// ERROR_NO_BUILD_PATH
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\217\340\256\242\240\253\250 \341\245 \341\352\247\244\240\242\240\255\245\342\256 \255\240 \250\255\341\342\240\253\240\346\250\256\255\255\240\342\240 \244\250\340\245\252\342\256\340\250\357 \247\240 ReactOS!\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
},
{
// ERROR_SOURCE_PATH
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245 \254\256\246\245\342\245 \244\240 \250\247\342\340\250\245\342\245 \244\357\253\240, \252\256\251\342\256 \341\352\244\352\340\246\240 \250\247\342\256\347\255\250\252\240 \255\240 \250\255\341\342\240\253\250\340\240\255\245!\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
},
{
// ERROR_SOURCE_DIR
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245 \254\256\246\245\342\245 \244\240 \250\255\341\342\240\253\250\340\240\342\245 ReactOS \242 \244\250\340\245\252\342\256\340\250\357\342\240 \255\240 \250\255\341\342\240\253\240\342\256\340\240!\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \256\342\252\340\250 \342\242\352\340\244 \244\250\341\252.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_SOURCE_DRIVE
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \256\342\252\340\250 \250\247\342\256\347\255\250\252 \247\240 \250\255\341\342\240\253\250\340\240\255\245.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_TXTSETUPSIF
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \255\240\254\245\340\250 \344\240\251\253\240 TXTSETUP.SIF.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CORRUPT_TXTSETUPSIF
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"TXTSETUP.SIF \245 \257\256\242\340\245\244\245\255.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_SIGNATURE_TXTSETUPSIF,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\217\256\244\257\250\341\240 \255\240 TXTSETUP.SIF \245 \255\245\242\240\253\250\244\245\255.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DRIVE_INFORMATION
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \255\240\254\245\340\250 \250\255\344\256\340\254\240\346\250\357 \247\240 \341\250\341\342\245\254\240\342\240.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_BOOT,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\240 \250\255\341\342\240\253\240\346\250\357 \255\240 \247\240\340\245\246\244\240\351\240\342\240 \257\340\256\243\340\240\254\240 \247\240 %S \242 \341\250\341\342\245\254\255\250\357 \244\357\253.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_COMPUTER,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \247\240\340\245\244\250 \341\257\250\341\352\252\240 \341 \342\250\257\256\242\245\342\245 \252\256\254\257\356\342\340\250.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_DISPLAY,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \247\240\340\245\244\250 \341\257\250\341\352\252\240 \341 \255\240\341\342\340\256\251\252\250 \255\240 \254\256\255\250\342\256\340\240.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KEYBOARD,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \254\256\246\240 \244\240 \247\240\340\245\244\250 \341\257\250\341\352\252\240 \341 \342\250\257\256\242\245\342\245 \252\253\240\242\250\240\342\343\340\250.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KBLAYOUT,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \247\240\340\245\244\250 \341\257\250\341\352\252\240 \341 \252\253\240\242\250\240\342\343\340\255\250\342\245 \257\256\244\340\245\244\241\250.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WARN_PARTITION,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \343\341\342\240\255\256\242\250, \347\245 \257\256\255\245 \245\244\250\255 \342\242\352\340\244 \244\250\341\252 \341\352\244\352\340\246\240 \255\245\341\352\242\254\245\341\342\250\254\240\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
"\244\357\253\256\242\240 \342\240\241\253\250\346\240, \341 \252\256\357\342\256 \255\245 \254\256\246\245 \244\240 \341\245 \340\240\241\256\342\250 \257\340\240\242\250\253\255\256!\n"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
"\221\352\247\244\240\242\240\255\245\342\256 \250\253\250 \250\247\342\340\250\242\240\255\245\342\256 \255\240 \244\357\253\256\242\245 \254\256\246\245 \244\240 \343\255\250\351\256\246\250 \244\357\253\256\242\240\342\240 \342\240\241\253\250\346\240.\n"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \x07 \207\240 \250\247\345\256\244 \255\240\342\250\341\255\245\342\245 F3.\n"
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \x07 \215\240\342\250\341\255\245\342\245 ENTER \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245.",
"F3 = \210\247\345\256\244 ENTER = \217\340\256\244\352\253\246\250"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245 \254\256\246\245\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \255\256\242 \244\357\253 \242 \244\250\341\252\240,\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
"\252\256\251\342\256 \242\245\347\245 \341\352\351\245\341\342\242\343\242\240!\n"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" * \215\240\342\250\341\255\245\342\245 \252\253\240\242\250\350, \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245.",
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245 \254\256\246\245\342\245 \247\240 \250\247\342\340\250\245\342\245 \255\245\247\240\244\245\253\245\255\256\342\256 \244\250\341\252\256\242\256 \254\357\341\342\256!\n"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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
" * \215\240\342\250\341\255\245\342\245 \252\253\240\242\250\350, \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245.",
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +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,
Bug 3033: patch for packmgr (kario@szm.sk) Bug 3039: Ukrainian translation update (temarez@yandex.ru) Bug 3041: Bulgarian translation of ReactOS. (sstpr@narod.ru) svn path=/trunk/; revision=32201
2008-02-07 21:23:46 +00:00
//"Setup failed to install the FAT bootcode on the system partition.",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\256 \250\255\341\342\240\253\250\340\240\255\245 \255\240 \341\342\240\340\342\250\340\240\351\240\342\240 \257\340\256\243\340\240\254\240 \242\352\242 FAT \247\240 %S \255\240 \341\250\341\342\245\254\255\250\357 \244\357\253.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_FLOPPY,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\202 \343\341\342\340\256\251\341\342\242\256 A: \255\357\254\240 \255\256\341\250\342\245\253.",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \217\340\256\244\352\253\246\250"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_KBSETTINGS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\215\245\343\341\257\245\350\255\256 \256\241\255\256\242\357\242\240\255\245 \255\240 \255\240\341\342\340\256\251\252\250\342\245 \255\240 \252\253\240\242\250\240\342\343\340\255\240\342\240 \257\256\244\340\245\244\241\240.",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_DISPLAY_SETTINGS,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\256 \256\241\255\256\242\357\242\240\255\245 \255\240 \255\240\341\342\340\256\251\252\250\342\245 \247\240 \254\256\255\250\342\256\340\240.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_IMPORT_HIVE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \252\256\257\250\340\240 \342\245\252\343\351\250\357 \344\240\251\253.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_FIND_REGISTRY
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\215\245 \241\357\345\240 \256\342\252\340\250\342\250 \344\240\251\253\256\242\245\342\245 \341 \340\245\243\250\341\342\352\340\255\250 \244\240\255\255\250.",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_HIVE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \255\240\254\245\340\250 \244\240\255\255\250 \247\240 \340\245\243\250\341\342\340\240\346\250\256\255\255\250\342\245 \344\240\251\253\256\242\245.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INITIALIZE_REGISTRY,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \341\352\247\244\240\244\245 \340\245\341\243\250\341\342\340\250\342\245.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INVALID_CABINET_INF,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"Cab \344\240\251\253\352\342 \255\357\254\240 \252\256\340\245\252\342\245\255 inf \344\240\251\253.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_MISSING,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"Cab \344\240\251\253\352\342 \255\245 \245 \255\240\254\245\340\245\255.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SCRIPT,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"Cab \344\240\251\253\352\342 \255\357\254\240 \341\252\340\250\257\342 \247\240 \250\255\341\342\240\253\240\346\250\357.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_COPY_QUEUE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \341\342\240\340\342\250\340\240 \252\256\257\250\340\240\255\245\342\256 \255\240 \344\240\251\253\256\242\245.\n",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_DIR,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\256 \341\352\247\244\240\242\240\255\245 \255\240 \257\240\257\252\250\342\245 \247\240 \250\255\341\342\240\253\250\340\240\255\245.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_TXTSETUP_SECTION,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \254\256\246\240 \244\240 \256\342\252\340\250\245 '%S'\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
"\242 TXTSETUP.SIF.\n",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SECTION,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \254\256\246\240 \244\240 \256\342\252\340\250\245 '%S'\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
"\242 cab \344\240\251\253\240.\n",
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_INSTALL_DIR
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\256 \341\352\247\244\240\242\240\255\245 \255\240 \257\240\257\252\240\342\240 \247\240 \250\255\341\342\240\253\240\346\250\357.",
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_PTABLE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \247\240\257\250\350\245 \344\240\251\253\256\242\240\342\240 \342\240\241\253\250\346\240.\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_CODEPAGE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \341\245 \257\340\256\242\240\253\250 \257\340\250 \244\256\241\240\242\357\255\245 \255\240 \252\256\244\256\242\240\342\240 \342\240\241\253\250\346\240 \242 \340\245\243\250\341\342\340\250\342\245.\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_LOCALESETTINGS,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\256 \250\255\341\342\240\253\250\340\240\255\245 \255\240 \253\256\252\240\253\255\250\342\245 \255\240\341\342\340\256\251\252\250.\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_KBLAYOUTS,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\343\341\257\245\350\255\256 \244\256\241\240\242\357\255\245 \255\240 \252\253\240\242\250\240\342\343\340\255\240\342\240 \257\256\244\340\245\244\241\240 \242 \340\245\243\250\341\342\352\340\240.\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
},
[usetup] - The last error messages were swapped in some languages, spotted by Paolo Devoti. - Added the minimum required disk space also in the debug print. See issue #5440 for more details. svn path=/trunk/; revision=47524
2010-06-02 22:28:37 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_GEOID,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \343\341\257\357 \244\240 \343\341\342\240\255\256\242\250 \243\245\256\243\340\240\344\341\252\256\342\256 \254\245\341\342\256\257\256\253\256\246\245\255\250\245.\n"
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
[usetup] - The last error messages were swapped in some languages, spotted by Paolo Devoti. - Added the minimum required disk space also in the debug print. See issue #5440 for more details. svn path=/trunk/; revision=47524
2010-06-02 22:28:37 +00:00
},
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DIRECTORY_NAME,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\242\240\253\250\244\255\256 \250\254\245 \255\240 \244\250\340\245\252\342\256\340\250\357\342\240.\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"
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" * \215\240\342\250\341\255\245\342\245 \257\340\256\250\247\242\256\253\245\255 \252\253\240\242\250\350, \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245."
[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
},
[USETUP] - Check for required minimum disk space eventually warn the user. - Added Italian and Spanish warnings, the other languages need translation. - Patch by R.T.Sivakumar modified by me. See issue #3302 for more details. svn path=/trunk/; revision=47341
2010-05-24 20:53:32 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INSUFFICIENT_PARTITION_SIZE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\202 \250\247\241\340\240\255\250\357 \244\357\253 \255\357\254\240 \244\256\341\342\240\342\352\347\255\256 \341\242\256\241\256\244\255\256 \254\357\341\342\256 \247\240 \250\255\341\342\240\253\240\346\250\357 \255\240 ReactOS.\n"
"\210\255\341\342\240\253\240\346\250\256\255\255\250\357 \244\357\253 \342\340\357\241\242\240 \244\240 \341\245 \341 \340\240\247\254\245\340 \255\240\251-\254\240\253\252\256 %lu MB.\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"
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" * \215\240\342\250\341\255\245\342\245 \257\340\256\250\247\242\256\253\245\255 \252\253\240\242\250\350, \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245.",
[USETUP] - Check for required minimum disk space eventually warn the user. - Added Italian and Spanish warnings, the other languages need translation. - Patch by R.T.Sivakumar modified by me. See issue #3302 for more details. svn path=/trunk/; revision=47341
2010-05-24 20:53:32 +00:00
NULL
},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_PARTITION_TABLE_FULL,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245 \254\256\246\245\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \255\256\242 \257\352\340\242\250\347\245\255 \250\253\250 \340\240\247\350\250\340\250\342\245\253\245\255 \244\357\253 \242\n"
"\247\240\351\256\342\256 \244\357\253\256\242\240\342\240 \342\240\241\253\250\346\240 \245 \257\352\253\255\240.\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"
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" * \215\240\342\250\341\255\245\342\245 \257\340\256\250\247\242\256\253\245\255 \252\253\240\242\250\350, \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245."
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245 \254\256\246\245\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \257\256\242\245\347\245 \256\342 \245\244\250\255 \340\240\247\350\250\340\250\342\245\253\245\255 \244\357\253.\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"
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" * \215\240\342\250\341\255\245\342\245 \257\340\256\250\247\242\256\253\245\255 \252\253\240\242\250\350, \247\240 \244\240 \257\340\256\244\352\253\246\250\342\245."
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357\342\240 \255\245 \254\256\246\245 \244\240 \344\256\340\254\240\342\250\340\240 \244\357\253\240:\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] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"
[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
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
NULL,
NULL
}
};
MUI_PAGE bgBGPages[] =
{
[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,
bgBGSetupInitPageEntries
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
LANGUAGE_PAGE,
bgBGLanguagePageEntries
},
{
[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,
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
bgBGWelcomePageEntries
},
{
INSTALL_INTRO_PAGE,
bgBGIntroPageEntries
},
{
LICENSE_PAGE,
bgBGLicensePageEntries
},
{
DEVICE_SETTINGS_PAGE,
bgBGDevicePageEntries
},
{
REPAIR_INTRO_PAGE,
bgBGRepairPageEntries
},
[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,
bgBGUpgradePageEntries
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
COMPUTER_SETTINGS_PAGE,
bgBGComputerPageEntries
},
{
DISPLAY_SETTINGS_PAGE,
bgBGDisplayPageEntries
},
{
FLUSH_PAGE,
bgBGFlushPageEntries
},
{
SELECT_PARTITION_PAGE,
bgBGSelectPartitionEntries
},
[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,
bgBGChangeSystemPartition
},
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
bgBGConfirmDeleteSystemPartitionEntries
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
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
SELECT_FILE_SYSTEM_PAGE,
bgBGSelectFSEntries
},
{
FORMAT_PARTITION_PAGE,
bgBGFormatPartitionEntries
},
[USETUP] Display the "check the FS" section as a MUI page (#3474)
2021-02-22 15:48:03 +00:00
{
CHECK_FILE_SYSTEM_PAGE,
bgBGCheckFSEntries
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
DELETE_PARTITION_PAGE,
bgBGDeletePartitionEntries
},
{
INSTALL_DIRECTORY_PAGE,
bgBGInstallDirectoryEntries
},
{
PREPARE_COPY_PAGE,
bgBGPrepareCopyEntries
},
{
FILE_COPY_PAGE,
bgBGFileCopyEntries
},
{
KEYBOARD_SETTINGS_PAGE,
bgBGKeyboardSettingsEntries
},
{
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
BOOTLOADER_SELECT_PAGE,
bgBGBootLoaderSelectPageEntries
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
LAYOUT_SETTINGS_PAGE,
bgBGLayoutSettingsEntries
},
{
QUIT_PAGE,
bgBGQuitPageEntries
},
{
SUCCESS_PAGE,
bgBGSuccessPageEntries
},
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
{
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
BOOTLOADER_INSTALL_PAGE,
[USETUP] Display some contents in the page whilst installing the bootloader (#3559) CORE-17523
2021-04-07 08:11:07 +00:00
bgBGBootLoaderInstallPageEntries
},
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
{
[USETUP] Decouple bootloader install choice page from its actual installation (#5786) This allows to move this choice sooner in the process, thus having all the user key presses at first, then all the actual installation going without any key presses needed anymore... (that is, unless you wanted to install the bootloader on a removable device. Then it will prompt you there!) - Additional "cosmetic"/future-proof changes: Rename all instances of "floppy" in the bootloader install variables to "RemovableDisk" because it would be great to have this install choice later. - Layout adjustments in the translated bootloader pages. - Skip bootloader installation on upgrades. The idea here is that if we were able to find a ReactOS installation to upgrade, this means we were able to find a valid bootloader + boot entry. See also PR #5633. This logic may be slightly improved in the future to detect whether the underlying bootloader is FreeLdr and if so, only update its files. But this is for the future.
2023-10-11 20:05:56 +00:00
BOOTLOADER_REMOVABLE_DISK_PAGE,
bgBGBootLoaderRemovableDiskPageEntries
Bug 2922: en-US updated shell translations (atylmo<AT>gmail<DOT>com) Bug 2957: Bulgarian translation of ReactOS (sstpr<AT>narod<DOT>ru) svn path=/trunk/; revision=31730
2008-01-12 10:20:26 +00:00
},
{
REGISTRY_PAGE,
bgBGRegistryEntries
},
{
-1,
NULL
}
};
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
MUI_STRING bgBGStrings[] =
{
{STRING_PLEASEWAIT,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \214\256\253\357 \250\247\347\240\252\240\251\342\245..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_INSTALLCREATEPARTITION,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" ENTER = \210\255\341\342\240\253\250\340\240\251 C = \221\352\247\244\240\251\342\245 \257\352\340\242\250\347\245\255 E = \221\352\247\244\240\251\342\245 \340\240\247\350\250\340\245\255 F3 = \210\247\345\256\244"},
[USETUP] - Add status text for logical partition entries in the partition list. - Add logical partition creation page dummy. svn path=/trunk/; revision=63570
2014-06-08 19:05:03 +00:00
{STRING_INSTALLCREATELOGICAL,
[USETUP] Further simplify partition creation UI code (#5837) - Use the same keypress 'C' to create either primary or logical partitions. Their type is automatically determined, whether they are created in general unpartitioned space, or space within an extended partition. - Extensively adapt the translations to reflect these changes.
2023-10-27 15:08:36 +00:00
" ENTER = \210\255\341\342\240\253\250\340\240\251 C = \221\352\247\244\240\251 \253\256\243\250\347\245\341\252\250 \257\240\340\342\250\350\352\255 F3 = \210\247\345\256\244"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_INSTALLDELETEPARTITION,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \210\255\341\342\240\253\250\340\240\251 D = \210\247\342\340\250\242\240\255\245 \255\240 \244\357\253 F3 = \210\247\345\256\244"},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" D = \210\247\342\340\250\251 \244\357\253 F3 = \210\247\345\256\244"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
"\220\240\247\254\245\340 \255\240 \255\256\242\250\357 \244\357\253:"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_CHOOSE_NEW_PARTITION,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\340\240\253\250 \341\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \255\256\242 \257\352\340\342\250\350\245\255 \244\357\253 \255\240"},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\340\240\253\250 \341\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \340\240\247\350\250\340\250\342\245\253\245\255 \244\357\253 \255\240"},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\340\240\253\250 \341\342\245 \244\240 \341\352\247\244\240\244\245\342\245 \253\256\243\250\347\245\341\252\250 \244\357\253 \255\240"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDPARTSIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\202\352\242\245\244\245\342\245 \340\240\247\254\245\340\240 \255\240 \255\256\242\250\357 \244\357\253 (\242 \254\245\243\240\241\240\251\342\250)."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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 = \221\352\247\244\240\242\240\255\245 \255\240 \244\357\253 ESC = \216\342\252\240\247 F3 = \210\247\345\256\244"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_NEWPARTITION,
"\201\245 \341\352\247\244\240\244\245\255 \255\256\242 \244\357\253 \255\240"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
"\217\340\245\244\341\342\256\250 \344\256\340\254\240\342\250\340\240\255\245 \255\240 \244\357\253\240."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_NONFORMATTEDPART,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\247\241\340\240\253\250 \341\342\245 \244\240 \341\253\256\246\250\342\245 ReactOS \255\240 \255\256\242 \250\253\250 \255\245\344\256\340\254\240\342\250\340\240\255 \244\357\253."},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\221\250\341\342\245\254\255\250\357\342 \244\357\253 \255\245 \245 \344\256\340\254\240\342\250\340\240\255 \242\341\245 \256\351\245."},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\256\242\250\357\342 \244\357\253 \255\245 \245 \344\256\340\254\240\342\250\340\240\255 \242\341\245 \256\351\245."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_INSTALLONPART,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\210\255\341\342\240\253\240\346\250\357 \255\240 ReactOS \242\352\340\345\343 \244\357\253"},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \217\340\256\244\352\253\246\250"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_QUITCONTINUE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"F3 = \210\247\345\256\244 ENTER = \217\340\256\244\352\253\246\250"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_REBOOTCOMPUTER,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_DELETING,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \210\247\342\340\250\242\240\255\245 \255\240 \344\240\251\253: %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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \214\245\341\342\250 \344\240\251\253: %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 Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \217\340\245\250\254\245\255\343\242\240 \344\240\251\253: %S to: %S"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
" \207\240\257\250\341 \255\240 \344\240\251\253: %S"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
"\224\240\251\253\256\242\245\342\245 \341\245 \247\240\257\250\341\242\240\342..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_REGHIVEUPDATE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \216\341\352\242\340\245\254\245\255\357\242\240\255\245 \255\240 \340\245\243\250\341\342\340\250\342\245..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_IMPORTFILE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \210\254\256\340\342\250\340\240\255\245 \255\240 %S..."},
[USETUP] Resources: fix a typo. svn path=/branches/setup_improvements/; revision=75748
2017-09-03 12:08:39 +00:00
{STRING_DISPLAYSETTINGSUPDATE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \216\341\352\242\340\245\254\245\255\357\242\240\255\245 \255\240 \255\240\341\342\340\256\251\252\250\342\245 \255\240 \245\252\340\240\255\240..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
" \216\341\352\242\340\245\254\245\255\357\242\240\255\245 \255\240 \254\245\341\342\255\250\342\245 \255\240\341\342\340\256\251\252\250..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
" \216\341\352\242\340\245\254\245\255\357\242\240\255\245 \255\240\341\342\340\256\251\252\250\342\245 \255\240 \252\253\240\242\250\240\342\343\340\255\250\342\245 \257\256\244\340\245\244\241\250..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
" \204\256\241\240\242\357\255\245 \242 \340\245\243\250\341\342\352\340\240 \255\240 \341\242\245\244\245\255\250\357 \247\240 \247\255\240\252\256\242\250\357 \255\240\241\256\340..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_DONE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \203\256\342\256\242\256..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_REBOOTCOMPUTER2,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" ENTER = \220\245\341\342\240\340\342\250\340\240\251 \252\256\254\257\356\342\352\340\240"},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \212\256\254\257\356\342\352\340\240 \351\245 \241\352\244\245 \340\245\341\342\240\340\342\250\340\240\255\245 \341\253\245\244 %li \341\245\252\343\255\244\250... "},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
"\216\342\242\240\340\357\255\245\342\256 \255\240 \252\256\255\247\256\253\240\342\240 \245 \255\245\242\352\247\254\256\246\255\256\r\n\r\n"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
"\222\256\242\240 \341\245 \341\253\343\347\242\240 \255\240\251- \347\245\341\342\256 \257\340\250 \343\257\256\342\340\245\241\240 \255\240 USB \252\253\240\242\250\240\342\343\340\240\r\n"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +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
"\217\256\244\244\340\352\246\252\240\342\240 \255\240 USB \245 \242\341\245 \256\351\245 \255\245\257\352\253\255\240\r\n"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_FORMATTINGPART,
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
2023-10-25 20:19:39 +00:00
"\224\256\340\254\240\342\250\340\240\255\245 \255\240 \244\357\253\240..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_CHECKINGDISK,
[USETUP] Show the partition description (and its disk) being formatted and checked (#5837) And improve some strings -- Translations need to be rechecked!
2023-10-25 20:19:39 +00:00
"\217\340\256\242\245\340\252\240 \255\240 \244\250\341\252\240..."},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_FORMATDISK1,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \224\256\340\254\240\342\250\340\240\255\245 \255\240 \244\357\253\240 \252\240\342\256 %S \344\240\251\253\256\242\240 \341\250\341\342\245\254\240 (\241\352\340\247\256 \344\256\340\254\240\342\250\340\240\255\245) "},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_FORMATDISK2,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \224\256\340\254\240\342\250\340\240\255\245 \255\240 \244\357\253\240 \252\240\342\256 %S \344\240\251\253\256\242\240 \341\250\341\342\245\254\240 "},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_KEEPFORMAT,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
" \207\240\257\240\247\242\240\255\245 \255\240 \344\240\251\253\256\242\240\342\240 \341\250\341\342\245\254\240 (\241\245\247 \257\340\256\254\245\255\250) "},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDISK1,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
"%s."},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDISK2,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
"\255\240: %s."},
{STRING_PARTTYPE,
"\242\250\244 0x%02x"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDINFO1,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
// "\342\242\352\340\244 \244\250\341\252 %lu (%I64u %s), \210\247\242\256\244=%hu, \230\250\255\240=%hu, \216\223=%hu (%wZ) [%s]"
"%I64u %s \342\242\352\340\244 \244\250\341\252 %lu (\210\247\242\256\244=%hu, \230\250\255\240=%hu, \216\223=%hu) \255\240 %wZ [%s]"},
[USETUP] Rename some MUI string identifiers (#5837) STRING_CHOOSENEWPARTITION --> STRING_CHOOSE_NEW_PARTITION STRING_FORMATTINGDISK --> STRING_FORMATTINGPART STRING_HDDSIZE --> STRING_HDPARTSIZE STRING_HDINFOPARTCREATE_1 --> STRING_HDDISK1 STRING_HDINFOPARTDELETE_1 --> STRING_HDDISK2 STRING_HDDINFO_{1,2} --> STRING_HDDINFO{1,2} Move STRING_NEWPARTITION just before STRING_PARTFORMAT and renumber the STRING_* identifiers.
2023-10-24 14:22:10 +00:00
{STRING_HDDINFO2,
[USETUP] Add partition and disk description helpers to get standardized description strings. Replace and simplify USETUP code.
2021-01-23 18:49:25 +00:00
// "\342\242\352\340\244 \244\250\341\252 %lu (%I64u %s), \210\247\242\256\244=%hu, \230\250\255\240=%hu, \216\223=%hu [%s]"
"%I64u %s \342\242\352\340\244 \244\250\341\252 %lu (\210\247\242\256\244=%hu, \230\250\255\240=%hu, \216\223=%hu) [%s]"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{STRING_UNPSPACE,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\215\245\247\240\244\245\253\245\255\256 \257\340\256\341\342\340\240\255\341\342\242\256"},
Once more, some more Strings open for translation. Have fun with 'em. svn path=/trunk/; revision=32423
2008-02-19 19:37:49 +00:00
{STRING_MAXSIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\214\201 (\244\256 %lu \214\201)"},
[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,
[TRANSLATION] Update Bulgarian translation (#4429) Update translations for: Explorer, Calculator, MSPaint, MSGina, USetup. Add translations for: INetCPL, Crypt32, CryptUI. Signed-off-by: Nikolay Dimitrov <delphipro@gmail.com> Co-authored-by: Hermès Bélusca-Maïto <hermes.belusca-maito@reactos.org> Reviewed-by: Rosen Iliev <winterhell2002@gmail.com>
2022-04-05 20:04:08 +00:00
"\220\240\247\350\250\340\245\255 \257\240\340\342\250\350\352\255"},
Once more, some more Strings open for translation. Have fun with 'em. svn path=/trunk/; revision=32423
2008-02-19 19:37:49 +00:00
{STRING_UNFORMATTED,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\215\256\242 (\215\245\344\256\340\254\240\342\250\340\240\255)"},
Once more, some more Strings open for translation. Have fun with 'em. svn path=/trunk/; revision=32423
2008-02-19 19:37:49 +00:00
{STRING_FORMATUNUSED,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\215\245\250\247\257\256\253\247\242\240\255"},
Once more, some more Strings open for translation. Have fun with 'em. svn path=/trunk/; revision=32423
2008-02-19 19:37:49 +00:00
{STRING_FORMATUNKNOWN,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\215\245\250\247\242\245\341\342\245\255"},
Okokok, I dont know why someone should feel the urge to translate MB, KB, and GB (Except specific languages...), but here they are. svn path=/trunk/; revision=32427
2008-02-19 21:31:09 +00:00
{STRING_KB,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\212\201"},
Okokok, I dont know why someone should feel the urge to translate MB, KB, and GB (Except specific languages...), but here they are. svn path=/trunk/; revision=32427
2008-02-19 21:31:09 +00:00
{STRING_MB,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\214\201"},
Okokok, I dont know why someone should feel the urge to translate MB, KB, and GB (Except specific languages...), but here they are. svn path=/trunk/; revision=32427
2008-02-19 21:31:09 +00:00
{STRING_GB,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\203\201"},
- Add support second keyboard layout - Update all translations svn path=/trunk/; revision=33175
2008-04-28 14:04:22 +00:00
{STRING_ADDKBLAYOUTS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\204\256\241\240\242\357\255\245 \255\240 \252\253\240\242\250\240\342\343\340\255\250 \257\256\244\340\245\244\241\250"},
Bug 3070: Ukrainian translation update by Artem Reznikov - temarez@yandex.ru Bug 3078: czech translation for solitaire by radekliska@gmail.com Bug 3083: usetup update by Paolo Devoti - devotip@tiscali.it Added the English Strings to all USETUP Resources and activated these. This makes translating easier. Renamed German to Deutsch and Russian to Russkij, which seems like it does not work... (thx to Caemyr anyway) svn path=/trunk/; revision=32406
2008-02-17 18:05:08 +00:00
{0, 0}
};
Reference in a new issue Copy permalink