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>".
2010-01-22 16:53:12 +00:00
/*
* translated by Artem Reznikov , Igor Paliychuk , 2010
* http : //www.reactos.org/uk/
2017-05-23 21:01:10 +00:00
*/
2010-01-22 16:53:12 +00:00
2010-02-26 11:43:19 +00:00
# pragma once
2007-12-15 11:25:03 +00:00
2018-12-23 19:28:19 +00:00
static MUI_ENTRY ukUASetupInitPageEntries [ ] =
{
{
4 ,
3 ,
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
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
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
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
2018-12-23 19:28:19 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-25 20:24:19 +00:00
static MUI_ENTRY ukUALanguagePageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-25 20:24:19 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \241 i \340 \254 \256 \242 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-25 20:24:19 +00:00
} ,
{
8 ,
10 ,
2018-12-20 08:25:32 +00:00
" \x07 \201 \343 \244 \354 - \253 \240 \341 \252 \240 , \242 \250 \241 \245 \340 i \342 \354 \254 \256 \242 \343 , \357 \252 \240 \241 \343 \244 \245 \242 \250 \252 \256 \340 \250 \341 \342 \240 \255 \240 \257 \340 \250 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 i. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-25 20:24:19 +00:00
} ,
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" \217 \256 \342 i \254 \255 \240 \342 \250 \341 \255 i \342 \354 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
2007-12-25 20:24:19 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \x07 \226 \357 \254 \256 \242 \240 \241 \343 \244 \245 \242 \250 \252 \256 \340 \250 \341 \342 \256 \242 \343 \242 \240 \342 \250 \341 \354 \343 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 i \251 \341 \250 \341 \342 \245 \254 i. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-25 20:24:19 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-25 20:24:19 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-15 11:25:03 +00:00
static MUI_ENTRY ukUAWelcomePageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \213 \240 \341 \252 \240 \242 \256 \257 \340 \256 \341 \250 \254 \256 \244 \256 \257 \340 \256 \243 \340 \240 \254 \250 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
6 ,
11 ,
2018-12-20 08:25:32 +00:00
" \215 \240 \346 \354 \256 \254 \343 \245 \342 \240 \257 i \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 \242 i \244 \241 \343 \244 \245 \342 \354 \341 \357 \252 \256 \257 i \356 \242 \240 \255 \255 \357 ReactOS \255 \240 \202 \240 \350 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
6 ,
12 ,
2018-12-20 08:25:32 +00:00
" \252 \256 \254 \257 ' \356 \342 \245 \340 i \257 i \244 \243 \256 \342 \256 \242 \252 \240 \244 \256 \244 \340 \343 \243 \256 \243 \256 \245 \342 \240 \257 \343 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
15 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \244 \253 \357 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 \240 \241 \256 \256 \255 \256 \242 \253 \245 \255 \255 \357 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
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
17 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 R \244 \253 \357 \256 \255 \256 \242 \253 \245 \255 \255 \357 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
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2007-12-15 11:25:03 +00:00
19 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 L \244 \253 \357 \257 \245 \340 \245 \243 \253 \357 \244 \343 \253 i \346 \245 \255 \247 i \251 \255 \250 \345 \343 \254 \256 \242 ReactOS. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 F3 \351 \256 \241 \242 \250 \251 \342 \250 . \255 \245 \242 \341 \342 \240 \255 \256 \242 \253 \356 \356 \347 \250 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
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
23 ,
2018-12-20 08:25:32 +00:00
" \204 \253 \357 \256 \342 \340 \250 \254 \240 \255 \255 \357 \244 \245 \342 \240 \253 \354 \255 i \350 \256 \365 i \255 \344 \256 \340 \254 \240 \346 i \365 \257 \340 \256 ReactOS, \241 \343 \244 \354 - \253 \240 \341 \252 \240 \242 i \244 \242 i \244 \240 \251 \342 \245 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
24 ,
2007-12-15 11:25:03 +00:00
" http://www.reactos.org/uk/ " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [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
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 R = \202 i \244 \255 \256 \242 \250 \342 \250 L = \213 i \346 \245 \255 \247 i \357 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUAIntroPageEntries [ ] =
{
{
2007-12-15 16:30:15 +00:00
4 ,
2007-12-15 11:25:03 +00:00
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \221 \342 \240 \255 \242 \245 \340 \341 i \365 ReactOS " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2018-06-11 20:53:57 +00:00
11 ,
2018-12-20 08:25:32 +00:00
" ReactOS \247 \255 \240 \345 \256 \244 \250 \342 \354 \341 \357 \242 \341 \342 \240 \244 i \365 \240 \253 \354 \344 \240 - \342 \245 \341 \342 \343 \242 \240 \255 \255 \357 , \241 i \253 \354 \350 i \341 \342 \354 \344 \343 \255 \252 \346 i \251 \351 \245 \255 \245 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
12 ,
2018-12-20 08:25:32 +00:00
" \244 \256 \242 \245 \244 \245 \255 i \244 \256 \243 \256 \342 \256 \242 \255 \256 \341 \342 i, \240 \253 \245 \365 \345 \340 \256 \247 \340 \256 \241 \252 \240 \251 \244 \245 \257 \256 \242 \255 \250 \254 \345 \256 \244 \256 \254 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2018-06-11 20:53:57 +00:00
6 ,
2007-12-15 11:25:03 +00:00
13 ,
2018-12-20 08:25:32 +00:00
" \215 \245 \340 \245 \252 \256 \254 \245 \255 \244 \343 \363 \342 \354 \341 \357 \242 \250 \252 \256 \340 \250 \341 \342 \256 \242 \343 \242 \240 \342 \250 \346 \356 \252 \256 \257 i \356 \244 \253 \357 \257 \256 \242 \341 \357 \252 \244 \245 \255 \255 \256 \243 \256 \252 \256 \340 \250 \341 \342 \343 \242 \240 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2018-06-11 20:53:57 +00:00
6 ,
15 ,
2018-12-20 08:25:32 +00:00
" \237 \252 \351 \256 \242 \250 \345 \256 \347 \245 \342 \245 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 \216 \221 \255 \240 \340 \256 \241 \256 \347 \256 \254 \343 \256 \241 \253 \240 \244 \255 \240 \255 \255 i, " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2018-06-11 20:53:57 +00:00
} ,
{
6 ,
16 ,
2018-12-20 08:25:32 +00:00
" \255 \245 \247 \240 \241 \343 \244 \354 \342 \245 \247 \241 \245 \340 \245 \243 \342 \250 \340 \245 \247 \245 \340 \242 \255 \343 \252 \256 \257 i \356 \242 \341 i \345 \242 \240 \350 \250 \345 \244 \240 \255 \250 \345 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2018-06-11 20:53:57 +00:00
19 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \244 \253 \357 \257 \340 \256 \244 \256 \242 \246 \245 \255 \255 \357 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 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
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2018-06-11 20:53:57 +00:00
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 F3 \351 \256 \241 \242 \250 \251 \342 \250 \255 \245 \242 \341 \342 \240 \255 \256 \242 \253 \356 \356 \347 \250 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
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
2007-12-15 16:30:15 +00:00
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \244 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUALicensePageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
6 ,
6 ,
2018-12-20 08:25:32 +00:00
" \213 i \346 \245 \255 \247 i \357 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
8 ,
2018-12-20 08:25:32 +00:00
" ReactOS \253 i \346 \245 \255 \247 \256 \242 \240 \255 \256 \242 i \244 \257 \256 \242 i \244 \255 \256 \244 \256 \343 \254 \256 \242 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
9 ,
2018-12-20 08:25:32 +00:00
" GNU GPL. \222 \240 \252 \256 \246 ReactOS \254 i \341 \342 \250 \342 \354 \252 \256 \254 \257 \256 \255 \245 \255 \342 \250 , \357 \252 i \253 i \346 \245 \255 \247 \256 \242 \240 \255 \256 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
10 ,
2018-12-20 08:25:32 +00:00
" \247 \240 \341 \343 \254 i \341 \255 \250 \254 \250 \253 i \346 \245 \255 \247 i \357 \254 \250 : X11, BSD, GNU LGPL. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \245 \257 \340 \256 \243 \340 \240 \254 \255 \245 \247 \240 \241 \245 \247 \257 \245 \347 \245 \255 \255 \357 , \357 \252 \245 \242 \345 \256 \244 \250 \342 \354 \242 \341 \250 \341 \342 \245 \254 \343 ReactOS, \242 \250 \257 \343 \351 \245 \255 \256 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
12 ,
2018-12-20 08:25:32 +00:00
" \257 i \244 \202 i \244 \252 \340 \250 \342 \256 \356 \253 i \346 \245 \255 \247 i \251 \255 \256 \356 \343 \243 \256 \244 \256 \356 GNU GPL i \247 \247 \241 \245 \340 \245 \246 \245 \255 \255 \357 \254 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \257 \245 \340 \242 \250 \255 \255 \250 \345 \253 i \346 \245 \255 \247 i \365 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
15 ,
2018-12-20 08:25:32 +00:00
" \204 \240 \255 \245 \257 \340 \256 \243 \340 \240 \254 \255 \245 \247 \240 \241 \245 \247 \257 \245 \347 \245 \255 \255 \357 \257 \256 \341 \342 \240 \242 \253 \357 \363 \342 \354 \341 \357 \201 \205 \207 \203 \200 \220 \200 \215 \222 I \365 i \241 \245 \247 \256 \241 \254 \245 \246 \245 \255 \354 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
16 ,
2018-12-20 08:25:32 +00:00
" \343 \242 \250 \252 \256 \340 \250 \341 \342 \240 \255 \255 i, \357 \252 \247 \240 \254 i \341 \346 \245 \242 \250 \254 , \342 \240 \252 i \254 i \246 \255 \240 \340 \256 \244 \255 \250 \254 \257 \340 \240 \242 \256 \254 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
17 ,
2018-12-20 08:25:32 +00:00
" \213 i \346 \245 \255 \247 i \357 ReactOS \244 \256 \247 \242 \256 \253 \357 \363 \257 \245 \340 \245 \244 \240 \347 \343 \257 \340 \256 \244 \343 \252 \342 \343 \342 \340 \245 \342 i \254 \256 \341 \256 \241 \240 \254 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
18 ,
2018-12-20 08:25:32 +00:00
" \237 \252 \351 \256 \347 \245 \340 \245 \247 \241 \343 \244 \354 - \357 \252 i \257 \340 \250 \347 \250 \255 \250 \202 \250 \255 \245 \256 \342 \340 \250 \254 \240 \253 \250 \252 \256 \257 i \356 \202 i \244 \252 \340 \250 \342 \256 \365 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
19 ,
2018-12-20 08:25:32 +00:00
" \253 i \346 \245 \255 \247 i \251 \255 \256 \365 \343 \243 \256 \244 \250 GNU \340 \240 \247 \256 \254 \247 ReactOS, \242 i \244 \242 i \244 \240 \363 \342 \245 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
8 ,
20 ,
" http://www.gnu.org/licenses/licenses.html " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
8 ,
22 ,
2018-12-20 08:25:32 +00:00
" \203 \240 \340 \240 \255 \342 i \365 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [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
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
8 ,
24 ,
2018-12-20 08:25:32 +00:00
" \226 \245 \363 \242 i \253 \354 \255 \245 \257 \340 \256 \243 \340 \240 \254 \255 \245 \247 \240 \241 \245 \247 \257 \245 \347 \245 \255 \255 \357 ; \244 \250 \242 . \244 \246 \245 \340 \245 \253 \256 \244 \253 \357 \257 \245 \340 \245 \243 \253 \357 \244 \343 \257 \340 \240 \242 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
8 ,
25 ,
2018-12-20 08:25:32 +00:00
" \215 \245 \244 \240 \356 \342 \354 \341 \357 \215 I \237 \212 I \243 \240 \340 \240 \255 \342 i \365 ; \255 i \243 \240 \340 \240 \255 \342 i \365 \222 \216 \202 \200 \220 \215 \216 \203 \216 \221 \222 \200 \215 \223 , \255 i " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
8 ,
26 ,
2018-12-20 08:25:32 +00:00
" \217 \220 \210 \204 \200 \222 \215 \216 \221 \222 I \204 \213 \237 \212 \216 \215 \212 \220 \205 \222 \215 \210 \225 \226 I \213 \205 \211 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \256 \242 \245 \340 \255 \343 \342 \250 \341 \354 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
2007-12-15 11:25:03 +00:00
} ,
2007-12-15 16:30:15 +00:00
{
2007-12-15 11:25:03 +00:00
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUADevicePageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
8 ,
2018-12-20 08:25:32 +00:00
" \223 \341 \257 \250 \341 \252 \343 \255 \250 \246 \347 \245 \257 \340 \250 \242 \245 \244 \245 \255 i \257 \256 \342 \256 \347 \255 i \257 \240 \340 \240 \254 \245 \342 \340 \250 \257 \340 \250 \341 \342 \340 \256 \365 \242 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
24 ,
2007-12-15 11:25:03 +00:00
11 ,
2018-12-20 08:25:32 +00:00
" \212 \256 \254 \257 ' \356 \342 \245 \340 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
24 ,
2007-12-15 11:25:03 +00:00
12 ,
2018-12-20 08:25:32 +00:00
" \205 \252 \340 \240 \255 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove 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
2007-12-15 11:25:03 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
24 ,
2007-12-15 11:25:03 +00:00
13 ,
2018-12-20 08:25:32 +00:00
" \212 \253 \240 \242 i \240 \342 \343 \340 \240 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
24 ,
2007-12-15 11:25:03 +00:00
14 ,
2018-12-20 08:25:32 +00:00
" \212 \253 \240 \242 . \340 \256 \247 \252 \253 \240 \244 \252 \240 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
24 ,
2007-12-15 11:25:03 +00:00
16 ,
2018-12-20 08:25:32 +00:00
" \217 \340 \250 \251 \255 \357 \342 \250 : " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_RIGHT ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
25 ,
2018-12-20 08:25:32 +00:00
16 , " \207 \240 \341 \342 \256 \341 \343 \242 \240 \342 \250 \244 \240 \255 i \257 \240 \340 \240 \254 \245 \342 \340 \250 \257 \340 \250 \341 \342 \340 \256 \365 \242 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
6 ,
19 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \254 \256 \246 \245 \342 \245 \247 \254 i \255 \250 \342 \250 \257 \240 \340 \240 \254 \245 \342 \340 \250 \257 \340 \250 \341 \342 \340 \256 \365 \242 \255 \240 \342 \250 \341 \252 \240 \356 \347 \250 \252 \253 \240 \242 i \350 i \202 \203 \216 \220 \223 i \202 \215 \210 \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
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
20 ,
2018-12-20 08:25:32 +00:00
" \244 \253 \357 \242 \250 \244 i \253 \245 \255 \255 \357 \245 \253 \245 \254 \245 \255 \342 \343 i \252 \253 \240 \242 i \350 \343 ENTER \244 \253 \357 \242 \250 \241 \256 \340 \343 i \255 \350 \250 \345 \242 \240 \340 i \240 \255 \342 i \242 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
21 ,
2018-12-20 08:25:32 +00:00
" \257 \240 \340 \240 \254 \245 \342 \340 i \242 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
23 ,
2018-12-20 08:25:32 +00:00
" \212 \256 \253 \250 \242 \341 i \257 \240 \340 \240 \254 \245 \342 \340 \250 \241 \343 \244 \343 \342 \354 \242 \250 \247 \255 \240 \347 \245 \255 i, \242 \250 \241 \245 \340 i \342 \354 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
24 ,
2018-12-20 08:25:32 +00:00
" \" \207 \240 \341 \342 \256 \341 \343 \242 \240 \342 \250 \244 \240 \255 i \257 \240 \340 \240 \254 \245 \342 \340 \250 \257 \340 \250 \341 \342 \340 \256 \365 \242 \" i \255 \240 \342 \250 \341 \255 i \342 \354 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
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUARepairPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
8 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 ReactOS \247 \255 \240 \345 \256 \244 \250 \342 \354 \341 \357 \242 \340 \240 \255 \255 i \251 \341 \342 \240 \244 i \365 \340 \256 \247 \340 \256 \241 \252 \250 i \351 \245 \255 \245 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
9 ,
2018-12-20 08:25:32 +00:00
" \257 i \244 \342 \340 \250 \254 \343 \363 \242 \341 i \344 \343 \255 \252 \346 i \365 \257 \256 \242 \255 \256 \346 i \255 \255 \256 \365 \257 \340 \256 \243 \340 \240 \254 \250 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
6 ,
2007-12-15 11:25:03 +00:00
12 ,
2018-12-20 08:25:32 +00:00
" \224 \343 \255 \252 \346 i \365 \242 i \244 \255 \256 \242 \253 \245 \255 \255 \357 \351 \245 \255 \245 \242 \257 \340 \256 \242 \240 \244 \246 \245 \255 i. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2007-12-15 11:25:03 +00:00
15 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 U \351 \256 \241 \256 \255 \256 \242 \250 \342 \250 OS. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2007-12-15 11:25:03 +00:00
17 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 R \244 \253 \357 \247 \240 \257 \343 \341 \252 \343 \212 \256 \255 \341 \256 \253 i \202 i \244 \255 \256 \242 \253 \245 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2007-12-15 11:25:03 +00:00
19 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \257 \256 \242 \245 \340 \255 \245 \255 \255 \357 \244 \256 \243 \256 \253 \256 \242 \255 \256 \365 \341 \342 \256 \340 i \255 \252 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
8 ,
2007-12-15 11:25:03 +00:00
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \257 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-15 16:30:15 +00:00
0 ,
2007-12-15 11:25:03 +00:00
0 ,
2018-12-20 08:25:32 +00:00
" ESC = \203 \256 \253 \256 \242 \255 \240 \221 \342 \256 \340 i \255 \252 \240 U = \216 \255 \256 \242 \250 \342 \250 R = \202 i \244 \255 \256 \242 \250 \342 \250 ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2015-12-27 15:22:39 +00:00
2017-05-15 01:48:19 +00:00
static MUI_ENTRY ukUAUpgradePageEntries [ ] =
{
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \217 \340 \256 \243 \340 \240 \254 \240 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 \254 \256 \246 \245 \256 \255 \256 \242 \250 \342 \250 \256 \244 \255 \343 i \247 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \250 \345 \252 \256 \257 i \251 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
2017-05-15 01:48:19 +00:00
} ,
{
6 ,
9 ,
2018-12-20 08:25:32 +00:00
" \257 \245 \340 \245 \340 \240 \345 \256 \242 \240 \255 \250 \345 \255 \250 \246 \347 \245 , \240 \241 \256 \357 \252 \351 \256 \242 \341 \342 \240 \255 \256 \242 \252 \240 ReactOS \257 \256 \350 \252 \256 \244 \246 \245 \255 \240 , \254 \256 \246 \255 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
6 ,
10 ,
2018-12-20 08:25:32 +00:00
" \341 \257 \340 \256 \241 \343 \242 \240 \342 \250 \242 i \244 \255 \256 \242 \250 \342 \250 \365 \365 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
6 ,
12 ,
2018-12-20 08:25:32 +00:00
" \224 \343 \255 \252 \346 i \357 \242 i \244 \255 \256 \242 \253 \245 \255 \255 \357 \242 \244 \240 \255 \250 \251 \254 \256 \254 \245 \255 \342 \242 i \244 \341 \343 \342 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_HIGHLIGHT ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
8 ,
15 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 \202 \202 \205 \220 \225 \240 \241 \256 \202 \215 \210 \207 \351 \256 \241 \256 \241 \340 \240 \342 \250 \252 \256 \253 \250 \350 \255 \356 \242 \341 \342 \240 \255 \256 \242 \252 \343 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
8 ,
17 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 U \244 \253 \357 \256 \255 \256 \242 \253 \245 \255 \255 \357 \256 \241 \340 \240 \255 \256 \365 \242 \341 \342 \240 \255 \256 \242 \252 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
8 ,
19 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \347 \250 \341 \342 \256 \365 \242 \341 \342 \240 \255 \256 \242 \252 \250 \216 \221 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
8 ,
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 F3 \351 \256 \241 \242 \250 \251 \342 \250 \255 \245 \242 \341 \342 \240 \255 \256 \242 \253 \356 \356 \347 \250 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
2017-05-15 01:48:19 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" U = \216 \255 \256 \242 \250 \342 \250 ESC = \217 \340 \256 \257 \343 \341 \342 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2017-05-15 01:48:19 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-15 11:25:03 +00:00
static MUI_ENTRY ukUAComputerPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \222 \343 \342 \202 \250 \254 \256 \246 \245 \342 \245 \247 \254 i \255 \250 \342 \250 \342 \250 \257 \202 \240 \350 \256 \243 \256 \252 \256 \254 \257 ' \356 \342 \245 \340 \240 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
10 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \252 \240 \251 \342 \245 \252 \253 \240 \242 i \350 i \202 \202 \205 \220 \225 \342 \240 \202 \215 \210 \207 \244 \253 \357 \242 \250 \241 \256 \340 \343 \342 \250 \257 \343 \202 \240 \350 \256 \243 \256 \252 \256 \254 \257 ' \356 \342 \245 \340 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 16:30:15 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" i \255 \240 \342 \250 \341 \255 i \342 \354 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
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \257 \256 \242 \245 \340 \255 \245 \255 \255 \357 \244 \256 \257 \256 \257 \245 \340 \245 \244 \255 \354 \256 \365 \341 \342 \256 \340 i \255 \252 \250 \241 \245 \247 \247 \254 i \255 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
14 ,
2018-12-20 08:25:32 +00:00
" \342 \250 \257 \343 \252 \256 \254 \257 ' \356 \342 \245 \340 \240 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUAFlushPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
10 ,
6 ,
2018-12-20 08:25:32 +00:00
" \221 \250 \341 \342 \245 \254 \240 \257 \245 \340 \245 \242 i \340 \357 \363 \347 \250 \242 \341 i \244 \240 \255 i \247 \241 \245 \340 \245 \246 \245 \255 \256 \255 \240 \244 \250 \341 \252 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
8 ,
2018-12-20 08:25:32 +00:00
" \226 \245 \254 \256 \246 \245 \247 \240 \251 \255 \357 \342 \250 \244 \245 \252 i \253 \354 \252 \240 \345 \242 \250 \253 \250 \255 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
9 ,
2018-12-20 08:25:32 +00:00
" \217 i \341 \253 \357 \247 \240 \242 \245 \340 \350 \245 \255 \255 \357 \252 \256 \254 \257 ' \356 \342 \245 \340 \241 \343 \244 \245 \240 \242 \342 \256 \254 \240 \342 \250 \347 \255 \256 \257 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \245 \255 \256 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" \216 \347 \250 \351 \343 \356 \252 \245 \350 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, 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
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUAQuitPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
10 ,
6 ,
2018-12-20 08:25:32 +00:00
" ReactOS \255 \245 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \256 \257 \256 \242 \255 i \341 \342 \356 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \342 \357 \243 \255 i \342 \354 \244 \250 \341 \252 \343 \342 \343 \247 \244 \250 \341 \252 \256 \242 \256 \244 \343 A: \342 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
9 ,
2018-12-20 08:25:32 +00:00
" \242 \341 i CD-ROM \247 CD- \257 \340 \250 \242 \256 \244 i \242 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
11 ,
2018-12-20 08:25:32 +00:00
" \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \257 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 \247 \240 \347 \245 \252 \240 \251 \342 \245 ... " ,
2010-01-22 16:53:12 +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
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUADisplayPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \222 \343 \342 \242 \250 \254 \256 \246 \245 \342 \245 \247 \254 i \255 \250 \342 \250 \342 \250 \257 \245 \252 \340 \240 \255 \343 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
2019-08-25 00:08:23 +00:00
{
8 ,
2007-12-15 11:25:03 +00:00
10 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \252 \240 \251 \342 \245 \252 \253 \240 \242 i \350 i \202 \202 \205 \220 \225 \342 \240 \202 \215 \210 \207 \244 \253 \357 \242 \250 \241 \256 \340 \343 \257 \256 \342 \340 i \241 \255 \256 \243 \256 \342 \250 \257 \343 \254 \256 \255 i \342 \256 \340 \343 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" i \255 \240 \342 \250 \341 \255 i \342 \354 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
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \257 \256 \242 \245 \340 \255 \245 \255 \255 \357 \244 \256 \257 \256 \257 \245 \340 \245 \244 \255 \354 \256 \365 \341 \342 \256 \340 i \255 \252 \250 \241 \245 \247 \247 \254 i \255 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
8 ,
14 ,
2018-12-20 08:25:32 +00:00
" \342 \250 \257 \343 \254 \256 \255 i \342 \256 \340 \240 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUASuccessPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
10 ,
6 ,
2018-12-20 08:25:32 +00:00
" \216 \341 \255 \256 \242 \255 i \252 \256 \254 \257 \256 \255 \245 \255 \342 \250 ReactOS \241 \343 \253 \250 \343 \341 \257 i \350 \255 \256 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 i. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \342 \357 \243 \255 i \342 \354 \244 \250 \341 \252 \245 \342 \343 \247 \244 \250 \341 \252 \256 \242 \256 \244 \343 A: \342 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
9 ,
2018-12-20 08:25:32 +00:00
" \242 \341 i CD-ROM \247 CD- \257 \340 \250 \242 \256 \244 i \242 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
10 ,
11 ,
2018-12-20 08:25:32 +00:00
" \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \257 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUABootPageEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-15 11:25:03 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \255 \245 \254 \256 \246 \245 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 bootloader \255 \240 \246 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
6 ,
9 ,
2018-12-20 08:25:32 +00:00
" \202 \240 \350 \256 \243 \256 \252 \256 \254 \257 ' \356 \342 \245 \340 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
6 ,
13 ,
2018-12-20 08:25:32 +00:00
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 \242 \341 \342 \240 \242 \342 \245 \242 i \244 \344 \256 \340 \254 \240 \342 \256 \242 \240 \255 \343 \244 \250 \341 \252 \245 \342 \343 \242 \244 \250 \242 \252 \256 \242 \256 \244 A: \342 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
6 ,
14 ,
2018-12-20 08:25:32 +00:00
" \255 \240 \342 \250 \341 \255 i \342 \354 ENTER. " ,
2008-03-19 04:43:40 +00:00
TEXT_STYLE_NORMAL ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-15 11:25:03 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-19 14:29:39 +00:00
static MUI_ENTRY ukUASelectPartitionEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \215 \250 \246 \347 \245 \257 \340 \250 \242 \245 \244 \245 \255 \250 \251 \341 \257 \250 \341 \256 \252 i \341 \255 \343 \356 \347 \250 \345 \340 \256 \247 \244 i \253 i \242 \342 \240 \255 \245 \247 \240 \251 \255 \357 \342 \256 \243 \256 \254 i \341 \346 \357 , \244 \245 \254 \256 \246 \255 \240 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
6 ,
9 ,
2018-12-20 08:25:32 +00:00
" \341 \342 \242 \256 \340 \250 \342 \250 \255 \256 \242 i \340 \256 \247 \244 i \253 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \252 \240 \251 \342 \245 \252 \253 \240 \242 i \350 i \202 \202 \205 \220 \225 \342 \240 \202 \215 \210 \207 \244 \253 \357 \242 \250 \241 \256 \340 \343 \257 \343 \255 \252 \342 \343 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 ReactOS \255 \240 \242 \250 \241 \340 \240 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
15 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 P \351 \256 \241 \341 \342 \242 \256 \340 \250 \342 \250 \257 \245 \340 \242 \250 \255 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
2014-05-20 23:48:36 +00:00
// "\x07 <20> <> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> i<EFBFBD> <69> C 鮡 <20> ⢮<EFBFBD> <E2A2AE> <EFBFBD> <EFBFBD> <20> <> <EFBFBD> <EFBFBD> <EFBFBD> <> i<EFBFBD> .",
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
17 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 E \351 \256 \241 \341 \342 \256 \242 \340 \250 \342 \250 \340 \256 \247 \350 \250 \340 \245 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2014-05-20 23:48:36 +00:00
} ,
{
8 ,
19 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 L \351 \256 \241 \341 \342 \242 \256 \340 \250 \342 \250 \253 \256 \243 i \347 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-07-04 16:04:09 +00:00
} ,
{
8 ,
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 D \351 \256 \241 \242 \250 \244 \240 \253 \250 \342 \250 i \341 \255 \343 \356 \347 \250 \251 \340 \256 \247 \244 i \253 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 , \247 \240 \347 \245 \252 \240 \251 \342 \245 ... " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2019-08-25 00:08:23 +00:00
static MUI_ENTRY ukUAChangeSystemPartition [ ] =
{
{
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
2019-08-25 00:08:23 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2016-02-28 02:51:47 +00:00
static MUI_ENTRY ukUAConfirmDeleteSystemPartitionEntries [ ] =
2015-08-09 13:14:00 +00:00
{
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \242 \250 \340 i \350 \250 \253 \250 \242 \250 \244 \240 \253 \250 \342 \250 \341 \250 \341 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
10 ,
2018-12-20 08:25:32 +00:00
" \221 \250 \341 \342 \245 \254 \255 i \340 \256 \247 \244 i \253 \250 \254 \256 \246 \343 \342 \354 \254 i \341 \342 \250 \342 \250 \244 i \240 \243 \255 \256 \341 \342 \250 \347 \255 i \257 \340 \256 \243 \340 \240 \254 \250 , \257 \340 \256 \243 \340 \240 \254 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
11 ,
2018-12-20 08:25:32 +00:00
" \255 \240 \253 \240 \350 \342 \343 \242 \240 \255 \255 \357 \240 \257 \240 \340 \240 \342 \255 \250 \345 \247 \240 \341 \256 \241 i \242 , \257 \340 \256 \243 \340 \240 \254 \250 \244 \253 \357 \247 \240 \257 \343 \341 \252 \343 \216 \221 ( \357 \252 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
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
12 ,
2018-12-20 08:25:32 +00:00
" \240 \241 \256 i \255 \350 \245 \217 \207 , \255 \240 \244 \240 \255 \245 \242 \250 \340 \256 \241 \255 \250 \252 \256 \254 \256 \241 \253 \240 \244 \255 \240 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
14 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \244 \240 \253 \357 \251 \342 \245 \341 \250 \341 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 , \252 \256 \253 \250 \242 \257 \245 \242 \255 \245 \255 i, \351 \256 \255 \240 \255 \354 \256 \254 \343 \255 \245 \254 \240 \363 \242 \240 \246 \253 \250 \242 \250 \345 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
15 ,
2018-12-20 08:25:32 +00:00
" \257 \340 \256 \243 \340 \240 \254 \240 \241 \256 \252 \256 \253 \250 \242 \250 \242 \257 \245 \242 \255 \245 \255 i, \351 \256 \242 \256 \255 \250 \255 \245 \257 \256 \342 \340 i \241 \255 i. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
16 ,
2018-12-20 08:25:32 +00:00
" \212 \256 \253 \250 \242 \250 \242 \250 \244 \240 \253 \250 \342 \245 \341 \250 \341 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 , \242 \250 \255 \245 \247 \254 \256 \246 \245 \342 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
6 ,
17 ,
2018-12-20 08:25:32 +00:00
" \252 \256 \254 \257 ' \356 \342 \245 \340 \247 \246 \256 \340 \341 \342 \252 \256 \243 \256 \244 \250 \341 \252 \240 , \257 \256 \252 \250 \255 \245 \247 \240 \252 i \255 \347 \250 \342 \245 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 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
2015-08-09 13:14:00 +00:00
} ,
{
8 ,
20 ,
2018-12-23 19:28:19 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \242 \250 \244 \240 \253 \250 \342 \250 \341 \250 \341 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
8 ,
21 ,
2018-12-20 08:25:32 +00:00
" \217 i \247 \255 i \350 \245 \202 \250 \257 \256 \242 \250 \255 \255 i \241 \343 \244 \245 \342 \245 \257 i \244 \342 \242 \245 \340 \244 \250 \342 \250 \242 \250 \244 \240 \253 \255 \255 \357 \247 \255 \256 \242 \343 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
8 ,
24 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \351 \256 \241 \257 \256 \242 \245 \340 \255 \343 \342 \250 \341 \354 \244 \256 \257 \256 \257 \245 \340 \245 \244 \255 \354 \256 \365 \341 \342 \256 \340 i \255 \252 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
8 ,
25 ,
2018-12-20 08:25:32 +00:00
" \220 \256 \247 \244 i \253 \255 \245 \241 \343 \244 \245 \242 \250 \244 \240 \253 \245 \255 \256 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER= \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 ESC= \221 \252 \240 \341 \343 \242 \240 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2015-08-09 13:14:00 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-19 14:29:39 +00:00
static MUI_ENTRY ukUAFormatPartitionEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \224 \256 \340 \254 \240 \342 \343 \242 \240 \255 \255 \357 \340 \256 \247 \244 i \253 \343 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
6 ,
10 ,
2018-12-20 08:25:32 +00:00
" \207 \240 \340 \240 \247 \242 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \242 i \244 \344 \256 \340 \254 \240 \342 \343 \363 \340 \256 \247 \244 i \253 . \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \244 \253 \357 \257 \340 \256 \244 \256 \242 \246 \245 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_FORMAT_PROMPT
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
2020-01-26 16:38:58 +00:00
0
2007-12-19 14:29:39 +00:00
}
} ;
2021-02-22 15:48:03 +00:00
static MUI_ENTRY ukUACheckFSEntries [ ] =
{
{
4 ,
3 ,
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
} ,
{
6 ,
8 ,
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \257 \245 \340 \245 \242 i \340 \357 \363 \242 \250 \241 \340 \240 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
} ,
{
0 ,
0 ,
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 , \247 \240 \347 \245 \252 \240 \251 \342 \245 ... " ,
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-19 14:29:39 +00:00
static MUI_ENTRY ukUAInstallDirectoryEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \242 \341 \342 \240 \255 \256 \242 \250 \342 \354 \344 \240 \251 \253 \250 ReactOS \255 \240 \242 \250 \241 \340 \240 \255 \250 \251 \340 \256 \247 \244 i \253 . \202 \250 \241 \245 \340 i \342 \354 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
6 ,
9 ,
2018-12-20 08:25:32 +00:00
" \244 \250 \340 \245 \252 \342 \256 \340 i \356 , \242 \357 \252 \343 \202 \250 \345 \256 \347 \245 \342 \245 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 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
2007-12-19 14:29:39 +00:00
} ,
{
6 ,
14 ,
2018-12-20 08:25:32 +00:00
" \231 \256 \241 \247 \254 i \255 \250 \342 \250 \244 \250 \340 \245 \252 \342 \256 \340 i \356 \255 \240 \342 \250 \341 \255 i \342 \354 BACKSPACE \244 \253 \357 \242 \250 \244 \240 \253 \245 \255 \255 \357 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
6 ,
15 ,
2018-12-20 08:25:32 +00:00
" \341 \250 \254 \242 \256 \253 i \242 \257 i \341 \253 \357 \347 \256 \243 \256 \242 \242 \245 \244 i \342 \354 \255 \240 \247 \242 \343 \244 \250 \340 \245 \252 \342 \256 \340 i \365 \244 \253 \357 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
6 ,
16 ,
2018-12-20 08:25:32 +00:00
" \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 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
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUAFileCopyEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
2010-01-22 16:53:12 +00:00
0 ,
2007-12-19 14:29:39 +00:00
12 ,
2018-12-20 08:25:32 +00:00
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 , \247 \240 \347 \245 \252 \240 \251 \342 \245 \257 \256 \252 \250 \242 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 ReactOS \252 \256 \257 i \356 \363 \344 \240 \251 \253 \250 \244 \256 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
0 ,
2007-12-19 14:29:39 +00:00
13 ,
2018-12-20 08:25:32 +00:00
" \257 \240 \257 \252 \250 \257 \340 \250 \247 \255 \240 \347 \245 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL | TEXT_ALIGN_CENTER ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
0 ,
2007-12-19 14:29:39 +00:00
14 ,
2018-12-20 08:25:32 +00:00
" \226 \245 \254 \256 \246 \245 \247 \240 \251 \255 \357 \342 \250 \244 \245 \252 i \253 \354 \252 \240 \345 \242 \250 \253 \250 \255 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove 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
2007-12-19 14:29:39 +00:00
} ,
{
2010-01-22 16:53:12 +00:00
50 ,
2007-12-19 14:29:39 +00:00
0 ,
2018-12-20 08:25:32 +00:00
" \xB3 \201 \343 \244 \354 - \253 \240 \341 \252 \240 \247 \240 \347 \245 \252 \240 \251 \342 \245 ... " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUABootLoaderEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \242 \341 \342 \240 \255 \256 \242 \253 \356 \363 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \347 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
12 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \250 \342 \250 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \347 \255 \240 \246 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 (MBR i 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
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \250 \342 \250 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \347 \255 \240 \246 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 ( \253 \250 \350 \245 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
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
14 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \250 \342 \250 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \347 \255 \240 \244 \250 \341 \252 \245 \342 \343 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2010-09-05 17:09:18 +00:00
} ,
{
8 ,
15 ,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \342 \250 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \347 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2021-04-07 08:11:07 +00:00
static MUI_ENTRY ukUABootLoaderInstallPageEntries [ ] =
{
{
4 ,
3 ,
" ReactOS " KERNEL_VERSION_STR " Setup " ,
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
} ,
{
0 ,
0 ,
" Installing the bootloader onto the media, please wait... " ,
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2007-12-19 14:29:39 +00:00
static MUI_ENTRY ukUAKeyboardSettingsEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \222 \343 \342 \202 \250 \254 \256 \246 \245 \342 \245 \247 \254 i \255 \250 \342 \250 \342 \250 \257 \252 \253 \240 \242 i \240 \342 \343 \340 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
10 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \252 \240 \251 \342 \245 \252 \253 \240 \242 i \350 i \202 \202 \205 \220 \225 \342 \240 \202 \215 \210 \207 \244 \253 \357 \242 \250 \241 \256 \340 \343 \257 \256 \342 \340 i \241 \255 \256 \243 \256 \342 \250 \257 \343 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" \252 \253 \240 \242 i \240 \342 \343 \340 \250 i \255 \240 \342 \250 \341 \255 i \342 \354 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
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \257 \256 \242 \245 \340 \255 \245 \255 \255 \357 \255 \240 \257 \256 \257 \245 \340 \245 \244 \255 \356 \341 \342 \256 \340 i \255 \252 \343 \241 \245 \247 \247 \254 i \255 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
14 ,
2018-12-20 08:25:32 +00:00
" \342 \250 \257 \343 \252 \253 \240 \242 i \240 \342 \343 \340 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUALayoutSettingsEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \241 \245 \340 i \342 \354 \340 \256 \247 \252 \253 \240 \244 \252 \343 , \357 \252 \240 \241 \343 \244 \245 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \240 \357 \252 \240 \341 \342 \240 \255 \244 \240 \340 \342 \255 \240 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
10 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \252 \240 \251 \342 \245 \252 \253 \240 \242 i \350 i \202 \202 \205 \220 \225 \342 \240 \202 \215 \210 \207 \244 \253 \357 \242 \250 \241 \256 \340 \343 \257 \256 \342 \340 i \241 \255 \256 \365 \340 \256 \247 \252 \253 \240 \244 \252 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
11 ,
2018-12-20 08:25:32 +00:00
" \252 \253 \240 \242 i \240 \342 \343 \340 \250 i \255 \240 \342 \250 \341 \255 i \342 \354 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
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
13 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \257 \256 \242 \245 \340 \255 \245 \255 \255 \357 \255 \240 \257 \256 \257 \245 \340 \245 \244 \255 \356 \341 \342 \256 \340 i \255 \252 \343 \241 \245 \247 \247 \254 i \255 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
14 ,
2018-12-20 08:25:32 +00:00
" \340 \256 \247 \252 \253 \240 \244 \252 \250 \252 \253 \240 \242 i \240 \342 \343 \340 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
} ,
} ;
static MUI_ENTRY ukUAPrepareCopyEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-23 19:28:19 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \243 \256 \342 \343 \363 \202 \240 \350 \252 \256 \254 \257 ' \356 \342 \245 \340 \244 \253 \357 \252 \256 \257 i \356 \242 \240 \255 \255 \357 \344 \240 \251 \253 i \242 ReactOS. " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" \203 \245 \255 \245 \340 \343 \356 \341 \257 \250 \341 \256 \252 \344 \240 \251 \253 i \242 ... " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
} ,
} ;
static MUI_ENTRY ukUASelectFSEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
17 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \241 \245 \340 i \342 \354 \344 \240 \251 \253 \256 \242 \343 \341 \250 \341 \342 \245 \254 \343 \247 i \341 \257 \250 \341 \252 \343 \255 \250 \246 \347 \245 . " ,
2007-12-19 14:29:39 +00:00
0
} ,
{
8 ,
19 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \252 \240 \251 \342 \245 \252 \253 \240 \242 i \350 i \202 \202 \205 \220 \225 \342 \240 \202 \215 \210 \207 \244 \253 \357 \242 \250 \241 \256 \340 \343 \344 \240 \251 \253 \256 \242 \256 \365 \341 \250 \341 \342 \245 \254 \250 . " ,
2007-12-19 14:29:39 +00:00
0
} ,
{
8 ,
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \242 i \244 \344 \256 \340 \254 \240 \342 \343 \242 \240 \342 \250 \340 \256 \247 \244 i \253 . " ,
2007-12-19 14:29:39 +00:00
0
} ,
{
8 ,
23 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \242 \250 \241 \256 \340 \343 i \255 \350 \256 \243 \256 \340 \256 \247 \244 i \253 \343 . " ,
2007-12-19 14:29:39 +00:00
0
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
static MUI_ENTRY ukUADeletePartitionEntries [ ] =
{
2007-12-31 17:56:13 +00:00
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2007-12-31 17:56:13 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
6 ,
8 ,
2018-12-20 08:25:32 +00:00
" \202 \250 \242 \250 \241 \340 \240 \253 \250 \242 \250 \244 \240 \253 \245 \255 \255 \357 \340 \256 \247 \244 i \253 \343 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
18 ,
2019-06-28 13:45:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 L \244 \253 \357 \242 \250 \244 \240 \253 \245 \255 \255 \357 \340 \256 \247 \244 i \253 \343 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
11 ,
19 ,
2018-12-20 08:25:32 +00:00
" \223 \202 \200 \203 \200 : \202 \341 i \244 \240 \255 i \255 \240 \346 \354 \256 \254 \343 \340 \256 \247 \244 i \253 i \241 \343 \244 \343 \342 \354 \242 \342 \340 \240 \347 \245 \255 i! " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
8 ,
21 ,
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ESC \244 \253 \357 \341 \252 \240 \341 \343 \242 \240 \255 \255 \357 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
2019-06-28 13:45:32 +00:00
" L = \202 \250 \244 \240 \253 \250 \342 \250 \220 \256 \247 \244 i \253 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2007-12-19 14:29:39 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
}
} ;
2008-01-02 15:07:27 +00:00
static MUI_ENTRY ukUARegistryEntries [ ] =
{
{
4 ,
3 ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS " KERNEL_VERSION_STR " " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_UNDERLINE ,
TEXT_ID_STATIC
2008-01-02 15:07:27 +00:00
} ,
{
6 ,
8 ,
2018-12-23 19:28:19 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \256 \255 \256 \242 \253 \356 \363 \252 \256 \255 \344 i \243 \343 \340 \240 \346 i \356 \341 \250 \341 \342 \245 \254 \250 . " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_STYLE_NORMAL ,
TEXT_ID_STATIC
2008-01-02 15:07:27 +00:00
} ,
{
0 ,
0 ,
2018-12-20 08:25:32 +00:00
" \221 \342 \242 \256 \340 \356 \356 \341 \342 \340 \343 \252 \342 \343 \340 \343 \340 \245 \363 \341 \342 \340 \343 ... " ,
[USETUP] Implement resource ID text based strings for MUI (#2193)
CORE-12683
Supersedes PR #612.
* [USETUP] Implement the internal MUI routines for text manipulation based on its ID and implement text resource based IDs
USETUP (the 1st stage text mode setup module) bases upon MUI (Multilingual User Interface) sub-component of USETUP which is responsible for the ability into translating the MUI pages (each page having corresponding properties like X, Y coordinates, text flags and text string buffer) in various languages.
The only problem, as of now, is that whenever you want to modify a certain property of a page, such as removing a text from the said page in the screen, you've got to rely on using CONSOLE_* specific functions and calling with hardcoded parameters, namely the coordinates.
This can become a problem as not every localized (translated) MUI page has the same properties for each language and this could lead to various issues. Therefore, assigning each entry with an ID you can remove a text by only giving its ID (and the entry page number) without having the need to specify the coordinates
as the internal MUI routine, MUIGetEntry(), automatically retrieves the entry with respective data fields.
The following commit implements:
- MUIGetEntry()
- MUIClearText()
- MUIClearStyledText()
- MUISetText()
- MUISetStyledText()
- Now the X and Y coordinate members of MUI_ENTRY are of SHORT integer type, for the sake of the general code as most of the coordination values, even the COORD structure itself, has the coordination points as SHORTs and not BYTEs.
The following MUI functions will be used to manipulate text based resources depending on their ID from the corresponding MUI entry.
* [USETUP] Make CONSOLE_ClearTextXY function public so that we can use across other files.
* [USETUP] Implement the IDs for each text MUI entry in locale files.
This mechanism follows the same principle of resource IDs in Win32 applications. Static text is merely a resource that doesn't get changed programmatically for whole of its lifetime whereas dynamic resources can change during the lifetime of the program depending on the algorithm (for example, hide that piece of text and set another one, etc.).
* [USETUP] Remove the "Press ENTER to continue" message prompt when the partition formatting begins.
2020-01-19 16:58:13 +00:00
TEXT_TYPE_STATUS | TEXT_PADDING_BIG ,
TEXT_ID_STATIC
2008-01-02 15:07:27 +00:00
} ,
{
0 ,
0 ,
NULL ,
0
} ,
} ;
2007-12-28 14:35:40 +00:00
MUI_ERROR ukUAErrorEntries [ ] =
{
2014-05-20 23:48:36 +00:00
{
// NOT_AN_ERROR
" Success \n "
} ,
2007-12-28 14:35:40 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_NOT_INSTALLED
2018-12-20 08:25:32 +00:00
" ReactOS \255 \245 \241 \343 \242 \257 \256 \242 \255 i \341 \342 \356 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \250 \251 \255 \240 \202 \240 \350 \n "
" \252 \256 \254 \257 ' \356 \342 \245 \340 . \237 \252 \351 \256 \242 \250 \242 \250 \251 \244 \245 \342 \245 \247 \242 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \240 \247 \240 \340 \240 \247 , \n "
" \342 \256 \202 \240 \254 \241 \343 \244 \245 \255 \245 \256 \241 \345 i \244 \255 \256 \247 \240 \257 \343 \341 \342 \250 \342 \250 \257 \340 \256 \243 \340 \240 \254 \343 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 \n "
" \247 \255 \256 \242 \343 , \357 \252 \351 \256 \202 \250 \345 \256 \347 \245 \342 \245 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 ReactOS, \n "
2008-01-07 21:34:56 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \257 \340 \256 \244 \256 \242 \246 \250 \342 \250 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 . \n "
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 F3 \244 \253 \357 \242 \250 \345 \256 \244 \343 \247 \242 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \240 . " ,
" F3 = \202 \250 \251 \342 \250 ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 "
2007-12-28 14:35:40 +00:00
} ,
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 "
} ,
2007-12-28 14:35:40 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_NO_HDD
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \255 \240 \251 \342 \250 \246 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_NO_SOURCE_DRIVE
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \255 \240 \251 \342 \250 \343 \341 \342 \240 \255 \256 \242 \256 \347 \255 \250 \251 \244 \250 \341 \252 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_TXTSETUPSIF
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \344 \240 \251 \253 TXTSETUP.SIF. \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CORRUPT_TXTSETUPSIF
2018-12-20 08:25:32 +00:00
" \224 \240 \251 \253 TXTSETUP.SIF \257 \256 \350 \252 \256 \244 \246 \245 \255 \250 \251 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_SIGNATURE_TXTSETUPSIF,
2018-12-20 08:25:32 +00:00
" \202 \250 \357 \242 \253 \245 \255 \256 \255 \245 \252 \256 \340 \245 \252 \342 \255 \250 \251 \257 i \244 \257 \250 \341 \242 TXTSETUP.SIF. \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_DRIVE_INFORMATION
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \256 \342 \340 \250 \254 \240 \342 \250 \244 \240 \255 i \257 \340 \256 \341 \250 \341 \342 \245 \254 \255 \250 \251 \244 \250 \341 \252 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_BOOT,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \253 \354 \255 \250 \251 \252 \256 \244 %S \255 \240 \341 \250 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_COMPUTER,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \341 \257 \250 \341 \256 \252 \342 \250 \257 i \242 \252 \256 \254 \257 ' \356 \342 \245 \340 \240 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_DISPLAY,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \341 \257 \250 \341 \256 \252 \340 \245 \246 \250 \254 i \242 \245 \252 \340 \240 \255 \343 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KEYBOARD,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \341 \257 \250 \341 \256 \252 \342 \250 \257 i \242 \252 \253 \240 \242 i \240 \342 \343 \340 \250 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_LOAD_KBLAYOUT,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \341 \257 \250 \341 \256 \252 \340 \256 \247 \252 \253 \240 \244 \256 \252 \252 \253 \240 \242 i \240 \342 \343 \340 \250 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_WARN_PARTITION,
2018-12-20 08:25:32 +00:00
" \207 \255 \240 \251 \244 \245 \255 \256 \357 \252 \254 i \255 i \254 \343 \254 \256 \244 \250 \255 \246 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 , \351 \256 \254 i \341 \342 \250 \342 \354 \340 \256 \247 \244 i \253 , \n "
" \357 \252 \250 \251 \255 \245 \257 i \244 \342 \340 \250 \254 \343 \363 \342 \354 \341 \357 ReactOS! \n "
2008-02-17 18:05:08 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" \221 \342 \242 \256 \340 \245 \255 \255 \357 \347 \250 \242 \250 \244 \240 \253 \245 \255 \255 \357 \340 \256 \247 \244 i \253 i \242 \254 \256 \246 \245 \247 \340 \343 \251 \255 \343 \242 \240 \342 \250 \342 \240 \241 \253 \250 \346 \356 \340 \256 \247 \244 i \253 i \242 . \n "
2008-02-17 18:05:08 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 F3 \244 \253 \357 \242 \250 \345 \256 \244 \343 \247 \242 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \240 . \n "
" \x07 \215 \240 \342 \250 \341 \255 i \342 \354 ENTER \351 \256 \241 \257 \340 \256 \244 \256 \242 \246 \250 \342 \250 . " ,
" F3 = \202 \250 \251 \342 \250 ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_NEW_PARTITION,
2018-12-20 08:25:32 +00:00
" \202 \250 \255 \245 \254 \256 \246 \245 \342 \245 \341 \342 \242 \256 \340 \250 \342 \250 \255 \256 \242 \250 \251 \340 \256 \247 \244 i \253 \255 \240 \n "
" \242 \246 \245 i \341 \255 \343 \356 \347 \256 \254 \343 \340 \256 \247 \244 i \253 i! \n "
2008-01-07 21:34:56 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" * \215 \240 \342 \250 \341 \255 i \342 \354 \241 \343 \244 \354 - \357 \252 \343 \252 \253 \240 \242 i \350 \343 \351 \256 \241 \257 \340 \256 \244 \256 \242 \246 \250 \342 \250 . " ,
2007-12-28 14:35:40 +00:00
NULL
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_DELETE_SPACE,
2018-12-20 08:25:32 +00:00
" \215 \245 \254 \256 \246 \255 \240 \242 \250 \244 \240 \253 \250 \342 \250 \255 \245 \340 \256 \247 \254 i \347 \245 \255 \343 \256 \241 \253 \240 \341 \342 \354 \255 \240 \244 \250 \341 \252 \343 ! \n "
2007-12-28 14:35:40 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" * \215 \240 \342 \250 \341 \255 i \342 \354 \241 \343 \244 \354 - \357 \252 \343 \252 \253 \240 \242 i \350 \343 \351 \256 \241 \257 \340 \256 \244 \256 \242 \246 \250 \342 \250 . " ,
2007-12-28 14:35:40 +00:00
NULL
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_INSTALL_BOOTCODE,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 \247 \240 \242 \240 \255 \342 \240 \246 \343 \242 \240 \253 \354 \255 \250 \251 \252 \256 \244 %S \255 \240 \341 \250 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_NO_FLOPPY,
2018-12-20 08:25:32 +00:00
" \202 i \244 \341 \343 \342 \255 \357 \244 \250 \341 \252 \245 \342 \240 \242 \244 \250 \341 \252 \256 \242 \256 \244 i A:. " ,
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_KBSETTINGS,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \256 \255 \256 \242 \250 \342 \250 \257 \240 \340 \240 \254 \245 \342 \340 \250 \340 \256 \247 \252 \253 \240 \244 \252 \250 \252 \253 \240 \242 i \240 \342 \343 \340 \250 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_DISPLAY_SETTINGS,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \256 \255 \256 \242 \250 \342 \250 \257 \240 \340 \240 \254 \245 \342 \340 \250 \245 \252 \340 \240 \255 \343 \242 \340 \245 \363 \341 \342 \340 i. " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_IMPORT_HIVE,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 i \254 \257 \256 \340 \342 \343 \242 \240 \342 \250 \344 \240 \251 \253 \252 \343 \351 i \242 \340 \245 \363 \341 \342 \340 \343 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_FIND_REGISTRY
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \255 \240 \251 \342 \250 \344 \240 \251 \253 \250 \244 \240 \255 \250 \345 \340 \245 \363 \341 \342 \340 \343 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_HIVE,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \341 \342 \242 \256 \340 \250 \342 \250 \252 \343 \351 i \340 \245 \363 \341 \342 \340 \343 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_INITIALIZE_REGISTRY,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 i \255 i \346 i \240 \253 i \247 \343 \242 \240 \342 \250 \340 \245 \363 \341 \342 \340 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_INVALID_CABINET_INF,
2018-12-20 08:25:32 +00:00
" Cabinet \254 \240 \363 \255 \245 \252 \256 \340 \245 \252 \342 \255 \250 \251 inf- \344 \240 \251 \253 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_MISSING,
2018-12-20 08:25:32 +00:00
" Cabinet \255 \245 \247 \255 \240 \251 \244 \245 \255 \256 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SCRIPT,
2018-12-20 08:25:32 +00:00
" Cabinet \255 \245 \254 \240 \363 \343 \341 \342 \240 \255 \256 \242 \256 \347 \255 \256 \243 \256 \341 \346 \245 \255 \240 \340 i \356 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_COPY_QUEUE,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \242 i \244 \252 \340 \250 \342 \250 \347 \245 \340 \243 \343 \252 \256 \257 i \356 \242 \240 \255 \255 \357 \344 \240 \251 \253 i \242 . \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_DIR,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \341 \342 \242 \256 \340 \250 \342 \250 \244 \250 \340 \245 \252 \342 \256 \340 i \365 \244 \253 \357 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_TXTSETUP_SECTION,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \255 \240 \251 \342 \250 \341 \245 \252 \346 i \356 '%S' \n "
" \242 \344 \240 \251 \253 i TXTSETUP.SIF. \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CABINET_SECTION,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \255 \240 \251 \342 \250 \341 \245 \252 \346 i \356 '%S' \n "
" \242 cabinet. \n " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_CREATE_INSTALL_DIR
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \341 \342 \242 \256 \340 \250 \342 \250 \244 \250 \340 \245 \252 \342 \256 \340 i \356 \244 \253 \357 \242 \341 \342 \240 \255 \256 \242 \253 \255 \255 \357 . " ,
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_WRITE_PTABLE,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \247 \240 \257 \250 \341 \240 \342 \250 \342 \240 \241 \253 \250 \346 i \340 \256 \247 \244 i \253 i \242 . \n "
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2007-12-28 14:35:40 +00:00
} ,
2008-01-07 14:51:42 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_CODEPAGE,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \244 \256 \244 \240 \342 \250 \257 \240 \340 \240 \254 \245 \342 \340 \250 \252 \256 \244 \343 \242 \240 \255 \255 \357 \242 \340 \245 \363 \341 \342 \340 . \n "
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2008-01-07 14:51:42 +00:00
} ,
2008-01-07 21:34:56 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_LOCALESETTINGS,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 \253 \256 \252 \240 \253 \354 \341 \250 \341 \342 \245 \254 \250 . \n "
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2008-01-07 21:34:56 +00:00
} ,
2008-04-28 14:04:22 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_ADDING_KBLAYOUTS,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \244 \256 \244 \240 \342 \250 \340 \256 \247 \252 \253 \240 \244 \252 \250 \252 \253 \240 \242 i \240 \342 \343 \340 \250 \244 \256 \340 \245 \363 \341 \342 \340 \343 . \n "
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2008-04-28 14:04:22 +00:00
} ,
2010-06-02 22:28:37 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_UPDATE_GEOID,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \242 \341 \342 \240 \255 \256 \242 \250 \342 \250 geo id. \n "
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2010-06-02 22:28:37 +00:00
} ,
2015-03-30 23:32:32 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_DIRECTORY_NAME,
2018-12-20 08:25:32 +00:00
" \215 \245 \257 \340 \240 \242 \250 \253 \354 \255 \240 \255 \240 \247 \242 \240 \244 \250 \340 \245 \252 \342 \256 \340 i \365 . \n "
2015-03-30 23:32:32 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" * \215 \240 \342 \250 \341 \255 i \342 \354 \241 \343 \244 \354 - \357 \252 \343 \252 \253 \240 \242 i \350 \343 \244 \253 \357 \257 \340 \256 \244 \256 \242 \246 \245 \255 \255 \357 . "
2015-03-30 23:32:32 +00:00
} ,
2010-05-24 20:53:32 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_INSUFFICIENT_PARTITION_SIZE,
2018-12-20 08:25:32 +00:00
" \216 \241 \340 \240 \255 \250 \251 \340 \256 \247 \244 i \253 \247 \240 \255 \240 \244 \342 \256 \254 \240 \253 \250 \251 \244 \253 \357 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS. \n "
" \202 \341 \342 \240 \255 \256 \242 \256 \347 \255 \250 \251 \340 \256 \247 \244 i \253 \257 \256 \242 \250 \255 \245 \255 \254 \240 \342 \250 \257 \340 \250 \255 \240 \251 \254 \255 i %lu MB \257 \340 \256 \341 \342 \256 \340 \343 . \n "
2014-12-27 12:33:59 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" * \215 \240 \342 \250 \341 \255 i \342 \354 \241 \343 \244 \354 - \357 \252 \343 \252 \253 \240 \242 i \350 \343 \244 \253 \357 \257 \340 \256 \244 \256 \242 \246 \245 \255 \255 \357 . " ,
2010-05-24 20:53:32 +00:00
NULL
} ,
2014-05-20 23:48:36 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_PARTITION_TABLE_FULL,
2018-12-20 08:25:32 +00:00
" \202 \250 \255 \245 \254 \256 \246 \245 \342 \245 \341 \342 \242 \256 \340 \250 \342 \250 \257 \245 \340 \242 \250 \255 \255 \250 \251 \240 \241 \256 \244 \256 \244 \240 \342 \252 \256 \242 \250 \251 \340 \256 \247 \244 i \253 \242 \342 \240 \241 \253 \250 \346 i \n "
" \340 \256 \247 \244 i \253 i \242 \244 \250 \341 \252 \343 , \342 \256 \254 \343 \351 \256 \242 \256 \255 \240 \247 \240 \257 \256 \242 \255 \245 \255 \240 . \n "
2014-05-20 23:48:36 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" * \215 \240 \342 \250 \341 \255 i \342 \354 \241 \343 \244 \354 - \357 \252 \343 \252 \253 \240 \242 i \350 \343 \244 \253 \357 \257 \340 \256 \244 \256 \242 \246 \245 \255 \255 \357 . " ,
2014-05-20 23:48:36 +00:00
} ,
{
2017-12-30 17:21:42 +00:00
// ERROR_ONLY_ONE_EXTENDED,
2018-12-20 08:25:32 +00:00
" \202 \250 \255 \245 \254 \256 \246 \245 \342 \245 \341 \342 \242 \256 \340 \250 \342 \250 \241 i \253 \354 \350 \245 \256 \244 \255 \256 \243 \256 \340 \256 \247 \350 \250 \340 \245 \255 \256 \243 \256 \340 \256 \247 \244 i \253 \343 \255 \240 \244 \250 \341 \252 . \n "
2014-05-20 23:48:36 +00:00
" \n "
2018-12-20 08:25:32 +00:00
" * \215 \240 \342 \250 \341 \255 i \342 \354 \241 \343 \244 \354 - \357 \252 \343 \252 \253 \240 \242 i \350 \343 \244 \253 \357 \257 \340 \256 \244 \256 \242 \246 \245 \255 \255 \357 . " ,
2014-05-20 23:48:36 +00:00
} ,
2015-07-11 12:40:34 +00:00
{
2017-12-30 17:21:42 +00:00
// ERROR_FORMATTING_PARTITION,
2018-12-20 08:25:32 +00:00
" \215 \245 \254 \256 \246 \253 \250 \242 \256 \242 i \244 \344 \256 \340 \254 \240 \342 \343 \242 \240 \342 \250 \340 \256 \247 \244 i \253 : \n "
2015-07-11 12:40:34 +00:00
" %S \n "
" \n "
2018-12-20 08:25:32 +00:00
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 "
2015-07-11 12:40:34 +00:00
} ,
2007-12-28 14:35:40 +00:00
{
NULL ,
NULL
}
} ;
2007-12-15 11:25:03 +00:00
MUI_PAGE ukUAPages [ ] =
{
2018-12-23 19:28:19 +00:00
{
SETUP_INIT_PAGE ,
ukUASetupInitPageEntries
} ,
2007-12-25 20:24:19 +00:00
{
LANGUAGE_PAGE ,
ukUALanguagePageEntries
} ,
2007-12-15 11:25:03 +00:00
{
2017-05-15 01:48:19 +00:00
WELCOME_PAGE ,
2008-02-17 18:05:08 +00:00
ukUAWelcomePageEntries
2007-12-15 11:25:03 +00:00
} ,
{
2007-12-19 11:37:35 +00:00
INSTALL_INTRO_PAGE ,
2007-12-15 11:25:03 +00:00
ukUAIntroPageEntries
} ,
{
LICENSE_PAGE ,
ukUALicensePageEntries
} ,
{
DEVICE_SETTINGS_PAGE ,
ukUADevicePageEntries
} ,
{
REPAIR_INTRO_PAGE ,
ukUARepairPageEntries
} ,
2017-05-15 01:48:19 +00:00
{
UPGRADE_REPAIR_PAGE ,
ukUAUpgradePageEntries
} ,
2007-12-15 11:25:03 +00:00
{
COMPUTER_SETTINGS_PAGE ,
ukUAComputerPageEntries
} ,
{
DISPLAY_SETTINGS_PAGE ,
ukUADisplayPageEntries
} ,
{
FLUSH_PAGE ,
ukUAFlushPageEntries
} ,
2007-12-19 14:29:39 +00:00
{
SELECT_PARTITION_PAGE ,
ukUASelectPartitionEntries
} ,
2019-08-25 00:08:23 +00:00
{
CHANGE_SYSTEM_PARTITION ,
ukUAChangeSystemPartition
} ,
2015-08-09 13:14:00 +00:00
{
CONFIRM_DELETE_SYSTEM_PARTITION_PAGE ,
2016-02-28 02:51:47 +00:00
ukUAConfirmDeleteSystemPartitionEntries
2015-08-09 13:14:00 +00:00
} ,
2007-12-19 14:29:39 +00:00
{
SELECT_FILE_SYSTEM_PAGE ,
ukUASelectFSEntries
} ,
{
FORMAT_PARTITION_PAGE ,
ukUAFormatPartitionEntries
} ,
2021-02-22 15:48:03 +00:00
{
CHECK_FILE_SYSTEM_PAGE ,
ukUACheckFSEntries
} ,
2007-12-19 14:29:39 +00:00
{
DELETE_PARTITION_PAGE ,
ukUADeletePartitionEntries
} ,
{
INSTALL_DIRECTORY_PAGE ,
ukUAInstallDirectoryEntries
} ,
{
PREPARE_COPY_PAGE ,
ukUAPrepareCopyEntries
} ,
{
FILE_COPY_PAGE ,
ukUAFileCopyEntries
} ,
{
KEYBOARD_SETTINGS_PAGE ,
ukUAKeyboardSettingsEntries
} ,
{
BOOT_LOADER_PAGE ,
ukUABootLoaderEntries
} ,
{
LAYOUT_SETTINGS_PAGE ,
ukUALayoutSettingsEntries
} ,
2007-12-15 11:25:03 +00:00
{
QUIT_PAGE ,
ukUAQuitPageEntries
} ,
{
SUCCESS_PAGE ,
ukUASuccessPageEntries
} ,
2021-04-07 08:11:07 +00:00
{
BOOT_LOADER_INSTALLATION_PAGE ,
ukUABootLoaderInstallPageEntries
} ,
2007-12-15 11:25:03 +00:00
{
BOOT_LOADER_FLOPPY_PAGE ,
ukUABootPageEntries
} ,
2008-01-02 15:07:27 +00:00
{
REGISTRY_PAGE ,
ukUARegistryEntries
} ,
2007-12-15 11:25:03 +00:00
{
- 1 ,
NULL
}
} ;
2008-02-17 18:05:08 +00:00
MUI_STRING ukUAStrings [ ] =
{
{ STRING_PLEASEWAIT ,
2018-12-20 08:25:32 +00:00
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 , \247 \240 \347 \245 \252 \240 \251 \342 \245 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_INSTALLCREATEPARTITION ,
2018-12-20 08:25:32 +00:00
" ENTER = \202 \341 \342 \240 \255 \256 \242 \250 \342 \250 P = \217 \245 \340 \242 \250 \255 \255 \250 \251 \340 \256 \247 \244 i \253 E = \220 \256 \247 \350 \250 \340 \245 \255 \250 \251 F3 = \202 \250 \251 \342 \250 " } ,
2014-05-20 23:48:36 +00:00
// " ENTER = <20> <> ⠭<EFBFBD> <E2A0AD> <EFBFBD> <EFBFBD> <EFBFBD> C = <20> ⢮<EFBFBD> <E2A2AE> <EFBFBD> <EFBFBD> <20> <> <EFBFBD> <EFBFBD> i<EFBFBD> F3 = <20> <> <EFBFBD> <EFBFBD> <EFBFBD> "},
2014-06-08 19:05:03 +00:00
{ STRING_INSTALLCREATELOGICAL ,
2018-12-20 08:25:32 +00:00
" ENTER = \202 \341 \342 \240 \255 \256 \242 \250 \342 \250 L = \221 \342 \242 \256 \340 \250 \342 \250 \253 \256 \243 i \347 \255 \250 \251 \340 \256 \247 \244 i \253 F3 = \202 \250 \251 \342 \250 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_INSTALLDELETEPARTITION ,
2018-12-20 08:25:32 +00:00
" ENTER = \202 \341 \342 \240 \255 \256 \242 \250 \342 \250 D = \202 \250 \244 \240 \253 \250 \342 \250 \340 \256 \247 \244 i \253 F3 = \202 \250 \251 \342 \250 " } ,
2014-05-20 23:48:36 +00:00
{ STRING_DELETEPARTITION ,
2018-12-20 08:25:32 +00:00
" D = \202 \250 \244 \240 \253 \250 \342 \250 \340 \256 \247 \244 i \253 F3 = \202 \250 \251 \342 \250 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_PARTITIONSIZE ,
2018-12-20 08:25:32 +00:00
" \220 \256 \247 \254 i \340 \255 \256 \242 \256 \243 \256 \340 \256 \247 \244 i \253 \343 : " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CHOOSENEWPARTITION ,
2018-12-20 08:25:32 +00:00
" \202 \250 \345 \256 \347 \245 \342 \245 \341 \342 \242 \256 \340 \250 \342 \250 \257 \245 \340 \242 \250 \255 \255 \250 \251 \340 \256 \247 \244 i \253 \255 \240 " } ,
2014-05-20 23:48:36 +00:00
// "<22> <> <20> <> <EFBFBD> <EFBFBD> <EFBFBD> <EFBFBD> <20> ⢮<EFBFBD> <E2A2AE> <EFBFBD> <EFBFBD> <20> <> <EFBFBD> <EFBFBD> <EFBFBD> <> i<EFBFBD> <20> <> "},
{ STRING_CHOOSE_NEW_EXTENDED_PARTITION ,
2018-12-20 08:25:32 +00:00
" \202 \250 \345 \256 \347 \245 \342 \245 \341 \342 \242 \256 \340 \250 \342 \250 \340 \256 \247 \350 \250 \340 \245 \255 \250 \251 \340 \256 \247 \244 i \253 \255 \240 " } ,
2014-06-09 01:49:24 +00:00
{ STRING_CHOOSE_NEW_LOGICAL_PARTITION ,
2018-12-20 08:25:32 +00:00
" \202 \250 \345 \256 \347 \245 \342 \245 \341 \342 \242 \256 \340 \250 \342 \250 \253 \256 \243 i \347 \255 \250 \251 \340 \256 \247 \244 i \253 \255 \240 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_HDDSIZE ,
2018-12-20 08:25:32 +00:00
" \201 \343 \244 \354 - \253 \240 \341 \252 \240 , \242 \242 \245 \244 i \342 \354 \340 \256 \247 \254 i \340 \255 \256 \242 \256 \243 \256 \340 \256 \247 \244 i \253 \343 \242 \254 \245 \243 \240 \241 \240 \251 \342 \240 \345 . " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CREATEPARTITION ,
2018-12-20 08:25:32 +00:00
" ENTER = \221 \342 \242 \256 \340 \250 \342 \250 \340 \256 \247 \244 i \253 ESC = \221 \252 \240 \341 \343 \242 \240 \342 \250 F3 = \202 \250 \251 \342 \250 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_PARTFORMAT ,
2018-12-20 08:25:32 +00:00
" \226 \245 \251 \340 \256 \247 \244 i \253 \241 \343 \244 \245 \242 i \244 \344 \256 \340 \254 \240 \342 \256 \242 \240 \255 \256 . " } ,
2008-02-17 18:05:08 +00:00
{ STRING_NONFORMATTEDPART ,
2018-12-20 08:25:32 +00:00
" \202 \250 \242 \250 \241 \340 \240 \253 \250 \242 \341 \342 \240 \255 \256 \242 \253 \245 \255 \255 \357 ReactOS \255 \240 \255 \256 \242 \250 \251 \240 \241 \256 \255 \245 \344 \256 \340 \254 \240 \342 \256 \242 \240 \255 \250 \251 \340 \256 \247 \244 i \253 . " } ,
2015-06-12 21:51:57 +00:00
{ STRING_NONFORMATTEDSYSTEMPART ,
2018-12-20 08:25:32 +00:00
" \221 \250 \341 \342 \245 \254 \255 \250 \251 \340 \256 \247 \244 i \253 \255 \245 \242 i \244 \344 \256 \340 \254 \240 \342 \256 \242 \240 \255 \256 . " } ,
2015-06-12 21:51:57 +00:00
{ STRING_NONFORMATTEDOTHERPART ,
2018-12-20 08:25:32 +00:00
" \215 \256 \242 \250 \251 \340 \256 \247 \244 i \253 \255 \245 \242 i \244 \344 \256 \340 \254 \240 \342 \256 \242 \240 \255 \256 . " } ,
2008-02-17 18:05:08 +00:00
{ STRING_INSTALLONPART ,
2018-12-20 08:25:32 +00:00
" ReactOS \242 \341 \342 \240 \255 \256 \242 \253 \356 \363 \342 \354 \341 \357 \255 \240 \340 \256 \247 \244 i \253 " } ,
2016-03-02 00:51:48 +00:00
{ STRING_CONTINUE ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_QUITCONTINUE ,
2018-12-20 08:25:32 +00:00
" F3 = \202 \250 \251 \342 \250 ENTER = \217 \340 \256 \244 \256 \242 \246 \250 \342 \250 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_REBOOTCOMPUTER ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 " } ,
2018-01-05 00:49:09 +00:00
{ STRING_DELETING ,
2018-12-20 08:25:32 +00:00
" \202 \250 \244 \240 \253 \245 \255 \255 \357 \344 \240 \251 \253 \343 : %S " } ,
2018-01-05 00:49:09 +00:00
{ STRING_MOVING ,
2018-12-20 08:25:32 +00:00
" \217 \245 \340 \245 \254 i \351 \245 \255 \255 \357 \344 \240 \251 \253 \343 : %S \242 : %S " } ,
2018-01-05 00:49:09 +00:00
{ STRING_RENAMING ,
2018-12-20 08:25:32 +00:00
" \217 \245 \340 \245 \251 \254 \245 \255 \343 \242 \240 \255 \255 \357 \344 \240 \251 \253 \343 : %S \242 : %S " } ,
2008-02-17 18:05:08 +00:00
{ STRING_COPYING ,
2018-12-20 08:25:32 +00:00
" \212 \256 \257 i \356 \242 \240 \255 \255 \357 : %S " } ,
2008-02-17 18:05:08 +00:00
{ STRING_SETUPCOPYINGFILES ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \252 \256 \257 i \356 \363 \344 \240 \251 \253 \250 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_REGHIVEUPDATE ,
2018-12-20 08:25:32 +00:00
" \216 \255 \256 \242 \253 \245 \255 \255 \357 \252 \343 \351 i \242 \340 \245 \363 \341 \342 \340 \343 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_IMPORTFILE ,
2018-12-20 08:25:32 +00:00
" I \254 \257 \256 \340 \342 \343 \242 \240 \255 \255 \357 %S... " } ,
2017-09-03 12:08:39 +00:00
{ STRING_DISPLAYSETTINGSUPDATE ,
2018-12-20 08:25:32 +00:00
" \216 \255 \256 \242 \253 \245 \255 \255 \357 \257 \240 \340 \240 \254 \245 \342 \340 i \242 \245 \252 \340 \240 \255 \343 \242 \340 \245 \363 \341 \342 \340 i... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_LOCALESETTINGSUPDATE ,
2018-12-20 08:25:32 +00:00
" \216 \255 \256 \242 \253 \245 \255 \255 \357 \257 \240 \340 \240 \254 \245 \342 \340 i \242 \253 \256 \252 \240 \253 i... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_KEYBOARDSETTINGSUPDATE ,
2018-12-20 08:25:32 +00:00
" \216 \255 \256 \242 \253 \245 \255 \255 \357 \257 \240 \340 \240 \254 \245 \342 \340 i \242 \340 \256 \247 \252 \253 \240 \244 \252 \250 \252 \253 \240 \242 i \240 \342 \343 \340 \250 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CODEPAGEINFOUPDATE ,
2018-12-20 08:25:32 +00:00
" \204 \256 \244 \240 \242 \240 \255 \255 \357 \244 \240 \255 \250 \345 \257 \340 \256 \252 \256 \244 \256 \242 \343 \341 \342 \256 \340 i \255 \252 \343 \242 \340 \245 \363 \341 \342 \340 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_DONE ,
2018-12-20 08:25:32 +00:00
" \203 \256 \342 \256 \242 \256 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_REBOOTCOMPUTER2 ,
2018-12-20 08:25:32 +00:00
" ENTER = \217 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \250 \342 \250 \252 \256 \254 \257 ' \356 \342 \245 \340 " } ,
2018-08-22 09:10:18 +00:00
{ STRING_REBOOTPROGRESSBAR ,
2018-12-20 08:25:32 +00:00
" \202 \240 \350 \252 \256 \254 \257 ' \356 \342 \245 \340 \241 \343 \244 \245 \257 \245 \340 \245 \247 \240 \242 \240 \255 \342 \240 \246 \245 \255 \256 \347 \245 \340 \245 \247 %li \341 \245 \252 \343 \255 \244 ... " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CONSOLEFAIL1 ,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \244 \240 \253 \256 \341 \354 \242 i \244 \252 \340 \250 \342 \250 \252 \256 \255 \341 \256 \253 \354 \r \n \r \n " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CONSOLEFAIL2 ,
2018-12-20 08:25:32 +00:00
" \215 \240 \251 \241 i \253 \354 \350 \251 \254 \256 \242 i \340 \255 \240 \257 \340 \250 \347 \250 \255 \240 \346 \354 \256 \243 \256 - \242 \250 \252 \256 \340 \250 \341 \342 \240 \255 \255 \357 USB \252 \253 \240 \242 i \240 \342 \343 \340 \250 \r \n " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CONSOLEFAIL3 ,
2018-12-20 08:25:32 +00:00
" USB \252 \253 \240 \242 i \240 \342 \343 \340 \250 \351 \245 \255 \245 \257 i \244 \342 \340 \250 \254 \343 \356 \342 \354 \341 \357 \257 \256 \242 \255 i \341 \342 \356 \r \n " } ,
2008-02-17 18:05:08 +00:00
{ STRING_FORMATTINGDISK ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \344 \256 \340 \254 \240 \342 \343 \363 \242 \240 \350 \244 \250 \341 \252 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_CHECKINGDISK ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \257 \245 \340 \245 \242 i \340 \357 \363 \242 \240 \350 \244 \250 \341 \252 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_FORMATDISK1 ,
2018-12-20 08:25:32 +00:00
" \224 \256 \340 \254 \240 \342 \343 \242 \240 \342 \250 \340 \256 \247 \244 i \253 \242 \344 \240 \251 \253 \256 \242 i \251 \341 \250 \341 \342 \245 \254 i %S ( \350 \242 \250 \244 \252 \245 \344 \256 \340 \254 \240 \342 \343 \242 \240 \255 \255 \357 ) " } ,
2008-02-17 18:05:08 +00:00
{ STRING_FORMATDISK2 ,
2018-12-20 08:25:32 +00:00
" \224 \256 \340 \254 \240 \342 \343 \242 \240 \342 \250 \340 \256 \247 \244 i \253 \242 \344 \240 \251 \253 \256 \242 i \251 \341 \250 \341 \342 \245 \254 i %S " } ,
2008-02-17 18:05:08 +00:00
{ STRING_KEEPFORMAT ,
2018-12-20 08:25:32 +00:00
" \207 \240 \253 \250 \350 \250 \342 \250 i \341 \255 \343 \356 \347 \343 \344 \240 \251 \253 \256 \242 \343 \341 \250 \341 \342 \245 \254 \343 ( \241 \245 \247 \247 \254 i \255 ) " } ,
2017-05-21 23:17:24 +00:00
{ STRING_HDINFOPARTCREATE_1 ,
2021-01-23 18:49:25 +00:00
" %s. " } ,
2017-05-21 23:17:24 +00:00
{ STRING_HDINFOPARTDELETE_1 ,
2021-01-23 18:49:25 +00:00
" \255 \240 : %s. " } ,
{ STRING_PARTTYPE ,
" Type 0x%02x " } ,
{ STRING_HDDINFO_1 ,
// "\206\256\340\341\342\252\250\251 \244\250\341\252 %lu (%I64u %s), \217\256\340\342=%hu, \230\250\255\240=%hu, Id=%hu (%wZ) [%s]"
" %I64u %s \206 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 %lu ( \217 \256 \340 \342 =%hu, \230 \250 \255 \240 =%hu, Id=%hu) \255 \240 %wZ [%s] " } ,
{ STRING_HDDINFO_2 ,
// "\206\256\340\341\342\252\250\251 \244\250\341\252 %lu (%I64u %s), \217\256\340\342=%hu, \230\250\255\240=%hu, Id=%hu [%s]"
" %I64u %s \206 \256 \340 \341 \342 \252 \250 \251 \244 \250 \341 \252 %lu ( \217 \256 \340 \342 =%hu, \230 \250 \255 \240 =%hu, Id=%hu) [%s] " } ,
2008-02-17 18:05:08 +00:00
{ STRING_NEWPARTITION ,
2018-12-20 08:25:32 +00:00
" \202 \341 \342 \240 \255 \256 \242 \253 \356 \242 \240 \347 \341 \342 \242 \256 \340 \250 \242 \255 \256 \242 \250 \251 \340 \256 \247 \244 i \253 \255 \240 " } ,
2008-02-17 18:05:08 +00:00
{ STRING_UNPSPACE ,
2021-01-23 18:49:25 +00:00
" \215 \245 \340 \256 \247 \254 i \347 \245 \255 \240 \256 \241 \253 \240 \341 \342 \354 " } ,
2008-02-19 19:37:49 +00:00
{ STRING_MAXSIZE ,
2018-12-20 08:25:32 +00:00
" MB ( \254 \240 \252 \341 . %lu MB) " } ,
2014-05-20 23:48:36 +00:00
{ STRING_EXTENDED_PARTITION ,
2018-12-20 08:25:32 +00:00
" \220 \256 \247 \350 \250 \340 \245 \255 \250 \251 \340 \256 \247 \244 i \253 " } ,
2008-02-19 19:37:49 +00:00
{ STRING_UNFORMATTED ,
2018-12-20 08:25:32 +00:00
" \215 \256 \242 \250 \251 ( \255 \245 \344 \256 \340 \254 \240 \342 \256 \242 \240 \255 \250 \251 ) " } ,
2008-02-19 19:37:49 +00:00
{ STRING_FORMATUNUSED ,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 \250 \252 \256 \340 \250 \341 \342 \240 \255 \256 " } ,
2008-02-19 19:37:49 +00:00
{ STRING_FORMATUNKNOWN ,
2018-12-20 08:25:32 +00:00
" \215 \245 \242 i \244 \256 \254 \256 " } ,
2008-02-19 21:31:09 +00:00
{ STRING_KB ,
" KB " } ,
{ STRING_MB ,
" MB " } ,
{ STRING_GB ,
" GB " } ,
2008-04-28 14:04:22 +00:00
{ STRING_ADDKBLAYOUTS ,
2018-12-20 08:25:32 +00:00
" \204 \256 \244 \240 \242 \240 \255 \255 \357 \340 \256 \247 \252 \253 \240 \244 \256 \252 \252 \253 \240 \242 i \240 \342 \343 \340 \250 " } ,
2008-02-17 18:05:08 +00:00
{ 0 , 0 }
} ;
