Intravision/reactos
1
0
Fork 0
mirror of https://github.com/reactos/reactos.git synced 2024-07-07 21:25:05 +00:00
Code Issues Packages Projects Releases Wiki Activity
reactos/base/setup/usetup/lang/tr-TR.h

2262 lines
52 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>".
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
/* TRANSLATORS: 2013-2015 Erdem Ersoy (eersoy93) (erdemersoy [at] live [dot] com), 2018 Ercan Ersoy (ercanersoy) (ercanersoy [at] ercanersoy [dot] net) */
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
- Move from using include guards to pragma once. - Whilst this is non-standard and potentially makes the code less portable, it's supported by both gcc and msvc and should bringg increased compilation speed due to its optimized behaviour (doesn't need to invoke the preprocessor) - Patch by Amine Khaldi [amine.khaldi@reactos.org] svn path=/trunk/; revision=45685
2010-02-26 11:43:19 +00:00
#pragma once
- Add more languages - Update languages svn path=/trunk/; revision=33814
2008-06-01 17:17:56 +00:00
[USETUP] Modify the integrated user-mode PnP manager along the lines of UMPNPMGR, so that we can wait until all the queued device installations finish before continuing the installation further. Add a corresponding please-wait page and update the translations.
2018-12-23 19:28:19 +00:00
static MUI_ENTRY trTRSetupInitPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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,
"Please wait while the ReactOS Setup initializes itself",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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,
"and discovers your devices...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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,
"Please wait...",
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
}
};
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
static MUI_ENTRY trTRLanguagePageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Dil Se\207imi",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 L\201tfen kurulum s\201reci i\207in kullan\215lacak dili se\207iniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Ard\215ndan ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Bu dil, kurulacak sistemin \224n tan\215ml\215 dili olacakt\215r.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRWelcomePageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"ReactOS Kur'a ho\237 geldiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
11,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kurulumun bu b\224l\201m\201, ReactOS \230\237letim Sistemi'ni bilgisayar\215n\215za",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"kopyalar ve kurulumun ikinci b\224l\201m\201n\201 haz\215rlar.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 ReactOS'u y\201klemek ya da y\201kseltmek i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 ReactOS'u onarmak veya y\201kseltmek i\207in R'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 ReactOS Lisans Terimleri'ni ve \236artlar\215'n\215 g\224r\201nt\201lemek i\207in L'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 ReactOS'u kurmadan \207\215kmak i\207in F3'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Daha \207ok bilgi i\207in l\201tfen u\247ray\215n\215z:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
24,
[USETUP] Update now-redirected 'http' and 'www.reactos.org' URLs (#2622) NB: http://www.reactos.org/uk/ is not updated, as it returns Error 404 - Page not found.
2020-04-22 05:44:13 +00:00
"https://reactos.org/",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r R = Onar veya Y\201kselt L = Lisans F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRIntroPageEntries[] =
{
{
4,
3,
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"ReactOS S\201r\201m Durumu",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
11,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS alfa a\237amas\215ndad\215r, \224zellikleri tamamlanmam\215\237 anlam\215na gelmektedir",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ve a\247\215r geli\237tirme alt\215ndad\215r. Yaln\215zca de\247erlendirme ve s\215nama ama\207lar\215yla",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
6,
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"kullan\215m\215 \224nerilmektedir ve g\201nl\201k kullan\215m i\237letim sisteminiz de\247ildir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
6,
15,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"E\247er, ReactOS'u ger\207ek donan\215m \201zerinde \207al\215\237t\215rmay\215 deneyecekseniz",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
},
{
6,
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"verilerinizi yedekleyin veya bir ikinci bilgisayar\215n\215zda s\215nay\215n.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - 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 ReactOS Kur'a s\201rd\201rmek i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
[USETUP] Display the ReactOS release status (#608) Update the introduction page with a more up-to-date exposition of the current status of ReactOS.
2018-06-11 20:53:57 +00:00
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - 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 ReactOS'u kurmaks\215z\215n \207\215kmak i\207in F3'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRLicensePageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
6,
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
"Lisanslama:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
8,
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
"ReactOS Sistemi, GNU GPL'yle X11, BSD ve GNU LPGL",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"lisanslar\215 gibi ba\237ka uygun lisanslardan kod i\207eren",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"b\224l\201mlerin \237artlar\215 alt\215nda lisanslanm\215\237t\215r.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Bu y\201zden ReactOS sisteminin b\224l\201m\201 olan t\201m yaz\215l\215mlar, korunan",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\224zg\201n lisanslar\215yla birlikte GNU GPL alt\215nda yay\215mlan\215r.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Bu yaz\215l\215m, yerel ve uluslararas\215 yasa uygulanabilir kullan\215m",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"\201zerine hi\207bir g\201vence ve k\215s\215tlamayla gelmez. ReactOS'un",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"lisanslanmas\215 yaln\215zca \201\207\201nc\201 yanlara da\247\215tmay\215 kapsar.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"E\247er birtak\215m nedenlerden dolay\215 ReactOS ile GNU Genel",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
18,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kamu Lisans\215'n\215n bir kopyas\215n\215 almad\215ysan\215z l\201tfen u\247ray\215n\215z:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
19,
"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
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"G\201vence:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
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
"Bu \224zg\201r yaz\215l\215md\215r, kopylama \237artlar\215 i\207in kayna\247a bak\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
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
"Burada hi\207bir g\201vence YOKTUR, SATILAB\230L\230RL\230K veya",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
25,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"BEL\230RL\230 B\230R AMACA UYGUNLUK i\207in bile.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = Geri D\224n",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRDevicePageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"A\237a\247\215daki liste \237imdiki ayg\215t ayarlar\215n\215 g\224sterir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
24,
11,
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
"Bilgisayar:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
24,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"G\224r\201nt\201:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
24,
13,
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
"Klavye:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
24,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Klavye D\201zeni:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
24,
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Do\247rula:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
25,
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
"Bu ayg\215t ayarlar\215n\215 do\247rula.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Ayg\215t ayarlar\215n\215, bir se\207enek se\207mek i\207in Yukar\215 veya A\237a\247\215",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"tu\237lar\215na basarak de\247i\237tirebilirsiniz. Sonra ba\237ka ayarlar se\207mek i\207in",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
{
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
6,
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER tu\237una bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"T\201m ayarlar uygun oldu\247unda ""Bu ayg\215t ayarlar\215n\215 do\247rula.""y\215",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +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
"se\207iniz ve ENTER tu\237una bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRRepairPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"ReactOS Kur, bir \224n geli\237me evresindedir. Daha t\201m\201yle kullan\215\237l\215",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"bir kurulum uygulamas\215n\215n t\201m i\237levlerini desteklemez.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Onarma i\237levleri daha bitirilmemi\237tir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 \230\237letim sistemini y\201kseltmek i\207in U'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Kurtarma Konsolu i\207in R'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Ana sayfaya geri d\224nmek i\207in ESC'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Bilgisayar\215n\215z\215 yeniden ba\237latmak i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"ESC = Ana Sayfa U = Y\201kselt R = Kurtarma ENTER = Yeniden Ba\237lat",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
[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 trTRUpgradePageEntries[] =
{
{
4,
3,
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS Kur, a\237a\247\215da listelenen bir mevcut ReactOS kurulumunu",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"y\201kseltebilir ya da ReactOS kurulumu zarar g\224rm\201\237se Kur program\215 onu",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"onarmay\215 deneyebilir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
6,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Onar\215m i\237levleri hen\201z tamamlanmam\215\237t\215r.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
15,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Bir i\237letim sistemi se\207mek i\207in YUKARI'ya ya da A\236A\246I'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Se\207ilmi\237 i\237letim sistemi kurulumunu y\201kseltmek i\207in U'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
19,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Bir yeni kuruluma s\201rd\201rmek i\207in ESC'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
8,
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - 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 ReactOS kurmaks\215z\215n \207\215kmak i\207in F3'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Add an upgrade/repair installation page. Translators, please update the associated translations! svn path=/branches/setup_improvements/; revision=74548
2017-05-15 01:48:19 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"U = Y\201kselt ESC = Y\201kseltme F3 = \200\215k\215\237",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
}
};
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
static MUI_ENTRY trTRComputerPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kurulum yap\215lacak bilgisayar\215n t\201r\201n\201 se\207mek isteyebilirsiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 \230stenen bilgisyar t\201r\201n\201 se\207mek i\207in YUKARI'ya veya A\236A\246I'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Ard\215ndan ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Bilgisayar t\201r\201n\201 de\247i\237tirmeden bir \224nceki sayfaya",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" d\224nmek i\207in ESC tu\237una bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r ESC = \230ptal F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRFlushPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
6,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Dizge, \237imdi diskinize saklanm\215\237 t\201m veriyi do\247ruluyor.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Bu bir dakika s\201rebilir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Bitti\247inde bilgisayar\215n\215z kendili\247inden yeniden ba\237layacakt\215r.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"\231n bellek temizleniyor...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRQuitPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
6,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS, t\201m\201yle kurulmad\215.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"A: s\201r\201c\201s\201nden disketi ve t\201m CD s\201r\201c\201lerinden",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"CD-ROM'lar\215 \207\215kart\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
11,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Bilgisayar\215n\215z\215 yeniden ba\237latmak i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"L\201tfen bekleyiniz...",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRDisplayPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kurulum yap\215lacak g\224r\201nt\201n\201n t\201r\201n\201 se\207mek isteyebilirsiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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,
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 \230stenen g\224r\201nt\201 t\201r\201n\201 se\207mek i\207in YUKARI'ya veya A\236A\246I'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Ard\215ndan ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 G\224r\201nt\201 t\201r\201n\201 de\247i\237tirmeden bir \224nceki sayfaya",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" d\224nmek i\207in ESC tu\237una bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r ESC = \230ptal F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRSuccessPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
6,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS'un ana bile\237enleri ba\237ar\215l\215 olarak kuruldu.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"A: s\201r\201c\201s\201nden disketi ve t\201m CD s\201r\201c\201lerinden",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
9,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"CD-ROM'lar\215 \207\215kart\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
10,
11,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Bilgisayar\215n\215z\215 yeniden ba\237latmak i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = Bilgisayar\215 Yeniden Ba\237lat",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRBootPageEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, bilgisayar\215n\215z\215n sabit diskine \224ny\201kleyiciyi kuramad\215.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"L\201tfen A: s\201r\201c\201s\201ne bi\207imlendirilmi\237 bir disket tak\215n\215z",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +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
"ve ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRSelectPartitionEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"A\237a\247\215daki liste, var olan b\224l\201mleri ve yeni b\224l\201mler i\207in",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"kullan\215lmayan disk bo\237lu\247unu g\224sterir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Bir liste girdisini se\207mek i\207in YUKARI'ya ya da A\236A\246I'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Se\207ili b\224l\201me ReactOS'u y\201klemek i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Bir ana b\224l\201m olu\237turmak i\207in P'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Bir geni\237letilmi\237 b\224l\201m olu\237turmak i\207in E'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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 Mant\215ksal bir b\224l\201m olu\237turmak i\207in L'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] - Add description of the 'L' key to the partition selection page. - Make the 'ENTER' key work for logical partitions too. Selected unpartitioned space will be converted to a logical partition. Patch by Gerhard Gruber (sparhawk). CORE-9641 #resolve svn path=/trunk/; revision=68339
2015-07-04 16:04:09 +00:00
},
{
8,
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\x07 Var olan bir b\224l\201m silmek i\207in D'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"L\201tfen bekleyiniz...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 trTRChangeSystemPartition[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Setup ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
8,
"The current system partition of your computer",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
12,
"on the system disk",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
16,
"uses a format not supported by ReactOS.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
18,
"In order to successfully install ReactOS, the Setup program must change",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
19,
"the current system partition to a new one.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
21,
"The new candidate system partition is:",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
25,
"\x07 To accept this choice, press ENTER.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
27,
"\x07 To manually change the system partition, press ESC to go back to",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
28,
" the partition selection list, then select or create a new system",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
8,
29,
" partition on the system disk.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
32,
"In case there are other operating systems that depend on the original",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
33,
"system partition, you may need to either reconfigure them for the new",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
34,
"system partition, or you may need to change the system partition back",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
6,
35,
"to the original one after finishing the installation of ReactOS.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
0,
0,
"ENTER = Continue ESC = Cancel",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG,
TEXT_ID_STATIC
[SETUPLIB][USETUP] Slightly modify how and when the HW system partition is detected and used. CORE-16274 SETUPLIB: ========= - Find the system partition initially when we create the list of partitions. - Split the old CheckActiveSystemPartition() helper in two helpers: FindSupportedSystemPartition() and SetActivePartition(). This allows simplifying slightly the former one, and allows the user, in an interactive situation, to decide whether the "supported system partition" found can actually be used or not. - Remove the "OriginalSystemPartition" hack in the PARTLIST structure. - Add a note regarding the SystemPartition member in PARTLIST. USETUP: ======= - Use the introduced helpers from above. If the "system" partition we are going to use, in case we install ReactOS on a fixed disk, is *NOT* the same as the original one (e.g. because it is detected to be not supported by ReactOS...), display an informative screen to the user and let him confirm whether or not he wants to change the partition. If we install on a fixed disk, try to find a supported system partition on the system. Otherwise if we install on a removable disk, use the install partition as the system partition instead. This allows providing a fix for CORE-16274.
2019-08-25 00:08:23 +00:00
},
{
0,
0,
NULL,
0
}
};
[USETUP]: Fix some translations (especially the french one). svn path=/trunk/; revision=70795
2016-02-28 02:51:47 +00:00
static MUI_ENTRY trTRConfirmDeleteSystemPartitionEntries[] =
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,
[TRANSLATION] Updating Turkish Translations by Erdem Ersoy CORE-9993 #resolve #comment Committed, thx. ^^ svn path=/trunk/; revision=68734
2015-08-17 12:05:10 +00:00
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur'a sistem b\224l\201m\201n\201 silmeyi sordunuz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sistem b\224l\201mleri; tan\215lama programlar\215, donan\215m yap\215land\215rma",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
11,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"programlar\215, ReactOS gibi bir i\237letim sistemini ba\237latmak i\207in programlar",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"veya donan\215m \201reticisi taraf\215ndan sa\247lanan ba\237ka programlar i\207erebilir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Yaln\215zca, b\224l\201mde b\224yle programlar\215n olmad\215\247\215ndan emin oldu\247unuzda ya da",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
15,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"onlar\215 silmek istedi\247inizden emin oldu\247unuzda bir sistem b\224l\201m\201n\201 siliniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
16,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"B\224l\201m\201 sildi\247inizde ReactOS Kur'u bitirene dek bilgisayar\215 sabit diskten",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
6,
17,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\224ny\201kleyemeyebilirsiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
20,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - 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 Sistem b\224l\201m\201n\201 silmek i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
21,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sonra b\224l\201m\201 silmeyi onaylamak i\207in yeniden sorulacaks\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
8,
24,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - 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 Bir \224nceki sayfaya d\224nmek i\207in ESC'e bas\215n\215z. B\224l\201m silinmeyecek.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
Show a warning page, when a user tries to delete an active partition. CORE-9996 #resolve svn path=/trunk/; revision=68652
2015-08-09 13:14:00 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r ESC = \230ptal",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
}
};
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
static MUI_ENTRY trTRFormatPartitionEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"B\224l\201m Bi\207imlendirme",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
{
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
6,
10,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, \237imdi b\224l\201m\201 bi\207imlendirecek. S\201rd\201rmek i\207in ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "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
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
}
};
static MUI_ENTRY trTRInstallDirectoryEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, se\207ili b\224l\201me ReactOS dosyalar\215n\215 y\201kler. ReactOS'un",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL,
TEXT_ID_STATIC
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"y\201klenmesini istedi\247iniz bir dizin se\207iniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
14,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\231nerilen dizini de\247i\237tirmek i\207in, karakterleri silmek i\207in BACKSPACE'e",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
15,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"bas\215n\215z ve ard\215ndan ReactOS'un y\201klenmesini istedi\247iniz dizini yaz\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRFileCopyEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS Kur, ReactOS kurulum dizininize dosyalar\215 kopyalarken",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
},
[USETUP]: Fix some localization problems. svn path=/trunk/; revision=70436
2015-12-27 15:22:39 +00:00
{
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
0,
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
" l\201tfen bekleyiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
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
"Bu, bitirmek i\207in birka\207 dakika s\201rebilir.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
50,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\xB3 L\201tfen bekleyiniz...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRBootLoaderEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, \224ny\201kleyiciyi kuruyor.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
8,
12,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\231ny\201kleyiciyi sabit diskin \201zerine kur. (MBR ve 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
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"\231ny\201kleyiciyi sabit diskin \201zerine kur. (Yaln\215zca 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
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"\231ny\201kleyiciyi bir diskete kur.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"\231ny\201kleyici kurulumunu ge\207.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRKeyboardSettingsEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kurulum yap\215lacak klavyenin t\201r\201n\201 se\207mek isteyebilirsiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 \230stenen klavye t\201r\201n\201 se\207mek i\207in YUKARI'ya veya A\236A\246I'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Ard\215ndan ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Klavye t\201r\201n\201 de\247i\237tirmeden bir \224nceki sayfaya",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" d\224nmek i\207in ESC tu\237una bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r ESC = \230ptal F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRLayoutSettingsEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
6,
8,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"L\201tfen \224ntan\215ml\215 olarak kurulacak bir d\201zen se\207iniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 \230stenen klavye d\201zenini se\207mek i\207in YUKARI'ya veya A\236A\246I'ya bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Ard\215ndan ENTER'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 G\224r\201nt\201 t\201r\201n\201 de\247i\237tirmeden bir \224nceki sayfaya",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" d\224nmek i\207in ESC d\201\247mesine bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r ESC = \230ptal F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY trTRPrepareCopyEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, ReactOS dosyalar\215n\215 kopyalamak i\207in bilgisayar\215n\215z\215 haz\215rl\215yor.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Dosya kopylalama listesi olu\237turuluyor...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
},
};
static MUI_ENTRY trTRSelectFSEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"A\237a\247\215daki listeden bir dosya sistemi se\207iniz.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Bir dosya sistemi se\207mek i\207in YUKARI'ya veya A\236A\246I'ya bas\215n\215z.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 B\224l\201m\201 bi\207imlendirmek i\207in ENTER'e bas\215n\215z.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Ba\237ka bir b\224l\201m se\207mek i\207in ESC'e bas\215n\215z.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
0
},
{
0,
0,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r ESC = \230ptal F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRDeletePartitionEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"B\224l\201m\201 silmeyi se\207tiniz.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 B\224l\201m\201 silmek i\207in L'ye bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"UYARI: Bu b\224l\201mdeki t\201m veriler yitirilecektir!",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 \230ptal etmek i\207in ESC'e bas\215n\215z.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 = B\224l\201m Sil ESC = \230ptal F3 = \200\215k",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
}
};
static MUI_ENTRY trTRRegistryEntries[] =
{
{
4,
3,
" ReactOS " KERNEL_VERSION_STR " Kur ",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, sistem yap\215land\215rmas\215n\215 g\201ncelle\237tiriyor.",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.). * [USETUP] Remove the "Press 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kay\215t y\215\247\215nlar\215 olu\237turuluyor...",
[USETUP] Implement resource ID text based strings for MUI (#2193) CORE-12683 Supersedes PR #612. * [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages. The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates. This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields. The following commit implements: - MUIGetEntry() - MUIClearText() - MUIClearStyledText() - MUISetText() - MUISetStyledText() - Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs. The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry. * [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files. * [USETUP] Implement the IDs for each text MUI entry in locale files. This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
0,
0,
NULL,
0
},
};
MUI_ERROR trTRErrorEntries[] =
{
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{
// NOT_AN_ERROR
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Ba\237ar\215l\215\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
},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NOT_INSTALLED
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS, bilgisayara t\201m\201yle kurulmad\215. E\247er \237imdi\n"
"Kur'dan \207\215karsan\215z ReactOS'u kurmak i\207in Kur'u\n"
"yeniden \207al\215\237t\215rmaya gereksinim duyacaks\215n\215z.\n"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Kur'u s\201rd\201rmek i\207in ENTER'e bas\215n\215z.\n"
" \x07 Kur'dan \207\215kmak i\207in F3'e bas\215n\215z.",
"F3 = \200\215k ENTER = S\201rd\201r"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
[USETUP] Localize the rest of the hardcoded error message strings
2019-02-13 16:13:48 +00:00
{
// ERROR_NO_BUILD_PATH
"Failed to build the installation paths for the ReactOS installation directory!\n"
"ENTER = Reboot computer"
},
{
// ERROR_SOURCE_PATH
"You cannot delete the partition containing the installation source!\n"
"ENTER = Reboot computer"
},
{
// ERROR_SOURCE_DIR
"You cannot install ReactOS within the installation source directory!\n"
"ENTER = Reboot computer"
},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_HDD
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, bir sabit disk bulamad\215.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NO_SOURCE_DRIVE
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kaynak s\201r\201c\201y\201 bulamad\215.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_TXTSETUPSIF
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, TXTSETUP.SIF dosyas\215n\215 y\201klemede ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
"Kur, bozuk bir TXTSETUP.SIF buldu.\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
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_SIGNATURE_TXTSETUPSIF,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, TXTSETUP.SIF'ta ge\207ersiz bir i\237aret buldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DRIVE_INFORMATION
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, sistem s\201r\201c\201 bilgisini alamad\215.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_BOOT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, sistem b\224l\201m\201ne %S \224ny\201kleme kodunu kuramad\215.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_COMPUTER,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, bilgisayar t\201r\201 sistemini y\201klemede ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_DISPLAY,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, g\224r\201nt\201 ayarlar\215 listesini y\201klemede ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KEYBOARD,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, klavye t\201r\201 listesini y\201klemede ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KBLAYOUT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, klavye d\201zeni listesini y\201klemede ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WARN_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, d\201zg\201n y\224netilemeyen bir uyumsuz b\224l\201m tablosu i\207eren en az\n"
[USETUP] Fix and add Turkish translation. (#1020)
2018-11-08 12:25:45 +00:00
"bir sabit disk buldu!\n"
[USETUP] Whitespace fixes only. svn path=/branches/setup_improvements/; revision=74636 svn path=/branches/setup_improvements/; revision=74639
2017-05-23 21:01:10 +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
"B\224l\201mleri olu\237turmak veya silmek b\224l\201m tablosunu yok edebilir.\n"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 Kur'dan \207\215kmak i\207in F3'e bas\215n\215z.\n"
" \x07 S\201rd\201rmek i\207in ENTER'e bas\215n\215z.",
"F3 = \200\215k ENTER = S\201rd\201r"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_NEW_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\231neden var olan bir b\224l\201m\201n i\207ine yeni\n"
"bir b\224l\201m olu\237turamazs\215n\215z!\n"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" * S\201rd\201rmek i\207in bir tu\237a bas\215n\215z.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
NULL
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DELETE_SPACE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"B\224l\201mlenmemi\237 disk bo\237lu\247unu silemezsiniz!\n"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" * S\201rd\201rmek i\207in bir tu\237a bas\215n\215z.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
NULL
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INSTALL_BOOTCODE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, sistem b\224l\201m\201 \201zerinde %S \224ny\201kleme kodunu kurmada ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"A: s\201r\201c\201s\201nde disk yok.",
"ENTER = S\201rd\201r"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, klavye d\201zeni ayarlar\215n\215 g\201ncelle\237tirmede ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_DISPLAY_SETTINGS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, g\224r\201nt\201 kay\215t ayarlar\215n\215 g\201ncelle\237tirmede ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_IMPORT_HIVE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, bir y\215\247\215n dosyas\215 almada ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, kay\215t veri dosyalar\215n\215 bulmada ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_HIVE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kay\215t y\215\247\215nlar\215n\215 olu\237turmada ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INITIALIZE_REGISTRY,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kay\215t defterini ba\237latmada ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INVALID_CABINET_INF,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Cabinet'in ge\207erli yap\215land\215rma dosyas\215 yok.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_MISSING,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Cabinet bulunamad\215.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SCRIPT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Cabinet kurulum beti\247i yok.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_COPY_QUEUE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, dosya kopyalamada kuyru\247unu a\207mada ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_DIR,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kurulum dizinlerini olu\237turmada ba\237ar\215s\215z oldu.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, TXTSETUP.SIF'de '%S' b\224l\201m\201n\201\n"
"bulmada ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, dolapta '%S' b\224l\201m\201n\201\n"
"bulmada ba\237ar\215s\215z oldu.\n",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_INSTALL_DIR
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kurulum dizinini olu\237turamad\215.",
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_PTABLE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, b\224l\201m tablolar\215 yazmada ba\237ar\215s\215z oldu.\n"
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_CODEPAGE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kay\215t defterine kod sayfas\215 eklemede ba\237ar\215s\215z oldu.\n"
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_LOCALESETTINGS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, sistem yerel ayar\215n\215 yapamad\215.\n"
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_KBLAYOUTS,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, kay\215t defterine klavye d\201zenleri eklemede ba\237ar\215s\215z oldu.\n"
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_GEOID,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, co\247rafi kimli\247i ayarlayamad\215.\n"
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
},
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_DIRECTORY_NAME,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Ge\207ersiz dizin ad\215.\n"
[USETUP]: Add basic installation directory validity check (only for whitespace for now). Patch by Edijs Kolesnikovics, see CORE-6149. Indeed, some ReactOS (and Windows as well) components do not support the system directory having spaces, in particular SMSS: this is due to the basic command-line parsing rules of SMSS that considers that the presence of a space in the command-line is equivalent to a separator, be it in or out a quoted string. svn path=/trunk/; revision=66995
2015-03-30 23:32:32 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * S\201rd\201rmek i\207in bir tu\237a bas\215n\215z."
[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] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_INSUFFICIENT_PARTITION_SIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Se\207ili b\224l\201m ReactOS'u kurmak i\207in yetecek \224l\207\201de b\201y\201k de\247il.\n"
"Kurulum b\224l\201m\201 en az %lu MB b\201y\201kl\201\247\201nde olmal\215.\n"
[USETUP] - Re-enable the partition size check and display a warning if the install partition is too small. - Update the required install partition size to 550MB. svn path=/trunk/; revision=65847
2014-12-27 12:33:59 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * S\201rd\201rmek i\207in bir tu\237a bas\215n\215z.",
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
NULL
},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_PARTITION_TABLE_FULL,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"B\224l\201m tablosu dolu oldu\247undan dolay\215 bu diskin b\224l\201m tablosunda yeni bir ana b\224l\201m\n"
"ya da yeni bir geni\237letilmi\237 b\224l\201m olu\237turamazs\215n\215z.\n"
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * S\201rd\201rmek i\207in bir tu\237a bas\215n\215z."
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
},
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_ONLY_ONE_EXTENDED,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Bir diskte birden \207ok geni\237letilmi\237 b\224l\201m olu\237turamazs\215n\215z.\n"
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" * S\201rd\201rmek i\207in bir tu\237a bas\215n\215z."
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
},
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
{
[SETUPLIB] Remove a deprecated error number (that gets merged with ERROR_TXTSETUP_SECTION). [USETUP] Improve usage of ERROR_TXTSETUP_SECTION and ERROR_CABINET_SECTION error codes, correctly display associated error message, and remove a deprecated string.
2017-12-30 17:21:42 +00:00
// ERROR_FORMATTING_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, b\224l\201m\201 bi\207imlendiremez:\n"
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
" %S\n"
"\n"
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - 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 = Bilgisayar\215 Yeniden Ba\237lat"
[USETUP] Show an error message if formatting a partition fails. Based on patch by mna. CORE-7969 #resolve #comment Thanks a lot! svn path=/trunk/; revision=68388
2015-07-11 12:40:34 +00:00
},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
NULL,
NULL
}
};
MUI_PAGE trTRPages[] =
{
[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,
trTRSetupInitPageEntries
},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
LANGUAGE_PAGE,
trTRLanguagePageEntries
},
{
[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,
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
trTRWelcomePageEntries
},
{
INSTALL_INTRO_PAGE,
trTRIntroPageEntries
},
{
LICENSE_PAGE,
trTRLicensePageEntries
},
{
DEVICE_SETTINGS_PAGE,
trTRDevicePageEntries
},
{
REPAIR_INTRO_PAGE,
trTRRepairPageEntries
},
[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,
trTRUpgradePageEntries
},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
COMPUTER_SETTINGS_PAGE,
trTRComputerPageEntries
},
{
DISPLAY_SETTINGS_PAGE,
trTRDisplayPageEntries
},
{
FLUSH_PAGE,
trTRFlushPageEntries
},
{
SELECT_PARTITION_PAGE,
trTRSelectPartitionEntries
},
[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,
trTRChangeSystemPartition
},
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
trTRConfirmDeleteSystemPartitionEntries
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
},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{
SELECT_FILE_SYSTEM_PAGE,
trTRSelectFSEntries
},
{
FORMAT_PARTITION_PAGE,
trTRFormatPartitionEntries
},
{
DELETE_PARTITION_PAGE,
trTRDeletePartitionEntries
},
{
INSTALL_DIRECTORY_PAGE,
trTRInstallDirectoryEntries
},
{
PREPARE_COPY_PAGE,
trTRPrepareCopyEntries
},
{
FILE_COPY_PAGE,
trTRFileCopyEntries
},
{
KEYBOARD_SETTINGS_PAGE,
trTRKeyboardSettingsEntries
},
{
BOOT_LOADER_PAGE,
trTRBootLoaderEntries
},
{
LAYOUT_SETTINGS_PAGE,
trTRLayoutSettingsEntries
},
{
QUIT_PAGE,
trTRQuitPageEntries
},
{
SUCCESS_PAGE,
trTRSuccessPageEntries
},
{
BOOT_LOADER_FLOPPY_PAGE,
trTRBootPageEntries
},
{
REGISTRY_PAGE,
trTRRegistryEntries
},
{
-1,
NULL
}
};
MUI_STRING trTRStrings[] =
{
{STRING_PLEASEWAIT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" L\201tfen bekleyiniz..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_INSTALLCREATEPARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ENTER = Kur P = Ana B\224l\201m Olu\237tur E = Geni\237letilmi\237 B\224l\201m Olu\237tur F3 = \200\215k"},
[USETUP] - Add status text for logical partition entries in the partition list. - Add logical partition creation page dummy. svn path=/trunk/; revision=63570
2014-06-08 19:05:03 +00:00
{STRING_INSTALLCREATELOGICAL,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ENTER = Kur L = Mant\215ksal B\224l\201m Olu\237tur F3 = \200\215k"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_INSTALLDELETEPARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ENTER = Kur D = B\224l\201m\201 Sil F3 = \200\215k"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_DELETEPARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" D = B\224l\201m\201 Sil F3 = \200\215k"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Yeni b\224l\201m\201n b\201y\201kl\201\247\201n\201 giriniz:"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_CHOOSENEWPARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\232zerinde bir ana b\224l\201m olu\237turmay\215 se\207tiniz:"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_CHOOSE_NEW_EXTENDED_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\232zerinde bir geni\237letilmi\237 b\224l\201m olu\237turmay\215 se\207tiniz:"},
[USETUP] Add the create logical partition page. svn path=/trunk/; revision=63574
2014-06-09 01:49:24 +00:00
{STRING_CHOOSE_NEW_LOGICAL_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\232zerinde bir mant\215ksal b\224l\201m olu\237turmay\215 se\207tiniz:"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_HDDSIZE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"L\201tfen yeni b\224l\201m\201n b\201y\201kl\201\247\201n\201 megabayt olarak giriniz."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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 = B\224l\201m Olu\237tur ESC = \230ptal F3 = \200\215k"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Bu b\224l\201m ileride bi\207imlendirilecektir."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_NONFORMATTEDPART,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ReactOS'u yeni ya da bi\207imlendirilmemi\237 bir b\224l\201me kurmay\215 se\207tiniz."},
[USETUP] - Implement mandatory filesystem selection, formatting and filesystem checks for all new partitons. - Implement optional filesystem selection, formatting and filesystem checks for formatted boot and install partitions. - Enable installing ReactOS on primary partitions other than the first one. Usetup will install Freeloader on the first (or active) partition (aka boot partition) and install ReactOS on the chosen partition (aka install partition). svn path=/trunk/; revision=68112
2015-06-12 21:51:57 +00:00
{STRING_NONFORMATTEDSYSTEMPART,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sistem b\224l\201m\201 daha bi\207imlendirilmemi\237."},
[USETUP] - Implement mandatory filesystem selection, formatting and filesystem checks for all new partitons. - Implement optional filesystem selection, formatting and filesystem checks for formatted boot and install partitions. - Enable installing ReactOS on primary partitions other than the first one. Usetup will install Freeloader on the first (or active) partition (aka boot partition) and install ReactOS on the chosen partition (aka install partition). svn path=/trunk/; revision=68112
2015-06-12 21:51:57 +00:00
{STRING_NONFORMATTEDOTHERPART,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Yeni b\224l\201m daha bi\207imlendirilmemi\237."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_INSTALLONPART,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, ReactOS'u b\224l\201m \201zerine kurar."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_CHECKINGPART,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, \237imdi se\207ili b\224l\201m\201 g\224zden ge\207iriyor."},
[USETUP]: In case chkdsk detects some disk errors, just display a warning message but allow the user to continue the installation. svn path=/trunk/; revision=70857
2016-03-02 00:51:48 +00:00
{STRING_CONTINUE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = S\201rd\201r"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_QUITCONTINUE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"F3 = \200\215k ENTER = S\201rd\201r"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_REBOOTCOMPUTER,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"ENTER = Bilgisayar\215 Yeniden Ba\237lat"},
[USETUP] Add new file-operation-related messages for deletion, moving and renaming.
2018-01-05 00:49:09 +00:00
{STRING_DELETING,
" Deleting file: %S"},
{STRING_MOVING,
" Moving file: %S to: %S"},
{STRING_RENAMING,
" Renaming file: %S to: %S"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Dosya kopyalan\215yor: %S"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kur, dosyalar\215 kopyal\215yor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_REGHIVEUPDATE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" Kay\215t y\215\247\215nlar\215 g\201ncelle\237tiriliyor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_IMPORTFILE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" Al\215n\215yor: %S..."},
[USETUP] Resources: fix a typo. svn path=/branches/setup_improvements/; revision=75748
2017-09-03 12:08:39 +00:00
{STRING_DISPLAYSETTINGSUPDATE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" G\224r\201nt\201 ayarlar\215 de\247erleri g\201ncelle\237tiriliyor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Yerel ayarlar g\201ncelle\237tiriliyor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Klavye d\201zeni ayarlar\215 g\201ncelle\237tiriliyor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
" Kay\215t defterine kod sayfas\215 bilgisi ekleniyor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_DONE,
[RAPPS] (for database) Many Improvements and Many Fixes by Erdem Ersoy + USETUP translation from Bug 7861. CORE-7710 #resolve #comment Committed, thx. svn path=/trunk/; revision=63814
2014-08-06 10:05:38 +00:00
" Bitti..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_REBOOTCOMPUTER2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" ENTER = Bilgisayar\215 Yeniden Ba\237lat"},
[USETUP] Implement the shutdown timeout progress bar. (#833) - Add the MUI ID resource. - Implement the shutdown timeout progress bar function and the TimeOut string handler. - Add the resource string to other resource languages.
2018-08-22 09:10:18 +00:00
{STRING_REBOOTPROGRESSBAR,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" Bilgisayar\215n\215z %li saniye sonra yeniden ba\237lat\215lacak... "},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Konsol a\207\215lam\215yor.\r\n\r\n"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Bunun en bilinen nedeni, bir USB klavye kullan\215lmas\215d\215r.\r\n"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_CONSOLEFAIL3,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"USB klavye daha t\201m\201yle desteklenmemektedir.\r\n"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_FORMATTINGDISK,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, diskinizi bi\207imlendiriyor."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_CHECKINGDISK,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, diskinizi g\224zden ge\207iriyor."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_FORMATDISK1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" B\224l\201m\201 %S dosya sistemiyle h\215zl\215 bi\207imlendir. "},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_FORMATDISK2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" B\224l\201m\201 %S dosya sistemiyle bi\207imlendir. "},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_KEEPFORMAT,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" \236imdiki dosya sistemini koru. (De\247i\237iklik yok.) "},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTCREATE_1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"%I64u %s Sabit Disk %lu (Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu), %wZ \201zerinde [%s]."},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTCREATE_2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"%I64u %s abit Disk %lu (Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu) [%s]."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_HDDINFOUNK2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" %c%c T\201r 0x%02X %I64u %s"},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTDELETE_1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\232zerinde: %I64u %s Sabit Disk %lu (Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu), %wZ \201zerinde [%s]."},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTDELETE_2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\232zerinde: %I64u %s Sabit Disk %lu (Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu) [%s]."},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTZEROED_1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Sabit Disk %lu (%I64u %s), Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu (%wZ) [%s]."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_HDDINFOUNK4,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"%c%c T\201r 0x%02X %I64u %s"},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTEXISTS_1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"\232zerinde: Sabit Disk %lu (%I64u %s), Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu (%wZ) [%s]."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_HDDINFOUNK5,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"%c%c %c %sT\201r %-3u%s %6lu %s"},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTSELECT_1,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"%6lu %s Sabit Disk %lu (Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu), %wZ \201zerinde [%s]"},
[USETUP] Rename some of the uninformative "STRING_HDDINFOUNKx" string labels into more informative ones. - Also, reserve a new field to display whether the disk is MBR or GPT-initialized. - Adjust the code that used the "STRING_HDDINFOUNKx" string labels. The extra slot added to some of the strings is to indicate whether the disk is MBR or GPT. As attentive readers will notice, the code that "determines" whether the disk is either MBR or GPT is of course just temporary: it's just a placeholder code that should currently just show "MBR". Having the NoMbr flag mostly signifies that the disk is uninitialized. A GPT disk also has a MBR but it's for "backcompatibility" / "protective" reasons (so that MBR-only tools would see the disk as just a big 1-partitioned only disk with which they could barely do anything). A real involved test for the nature of the disk should involve calling the correct IOCTLs in the disk detection code in partlist.c . This is for the future (and when ReactOS will better support GPT disks). svn path=/branches/setup_improvements/; revision=74614 svn path=/branches/setup_improvements/; revision=74615
2017-05-21 23:17:24 +00:00
{STRING_HDINFOPARTSELECT_2,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"%6lu %s Sabit Disk %lu (Giri\237=%hu, Veriyolu=%hu, Kimlik=%hu) [%s]"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_NEWPARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Kur, \201zerinde bir yeni b\224l\201m olu\237turdu:"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_UNPSPACE,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
" %sKullan\215lmayan Bo\237luk%s %6lu %s"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"MB (En \207ok %lu MB)"},
[USETUP] - Implement creation of extended partitions. - Add creation checks for primary and extended partitions. svn path=/trunk/; revision=63392
2014-05-20 23:48:36 +00:00
{STRING_EXTENDED_PARTITION,
[USETUP][NTDLL_APITEST][KBDROST] Allow non-Latin codepage users to build ReactOS on MSVC (Retrial of #1150) (#1168) - The converter is code7bit I made. code7bit: https://github.com/katahiromz/code7bit - This converter converts non-clean characters in string literals. - However I couldn't erase a ton of codepage C4819 warnings. - CORE-15447 You can edit an European source file as follows: - Right click the file in the Solution Explorer. - Select "Open With...". - Choose "C++ Source Code Editor (with encoding)". - Choose "Central European (Windows) - Codepage 1260".
2018-12-20 08:25:32 +00:00
"Geni\237letilmi\237 B\224l\201m"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Yeni (Bi\207imlendirilmemi\237)"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +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
"Kullan\215lmayan"},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{STRING_FORMATUNKNOWN,
"Bilinmeyen"},
{STRING_KB,
"KB"},
{STRING_MB,
"MB"},
{STRING_GB,
"GB"},
{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
"Klavye d\201zenleri ekleniyor..."},
[USETUP] Apply turkish ranslation. Patch by Erdem Ersoy. CORE-7408 #comment Usetup translation applied in r60914. Thanks a lot! svn path=/trunk/; revision=60914
2013-11-10 14:16:05 +00:00
{0, 0}
};
Reference in a new issue Copy permalink