Hubbry Logo
Windows-1250Windows-1250Main
Open search
Windows-1250
Community hub
Windows-1250
logo
7 pages, 0 posts
0 subscribers
Be the first to start a discussion here.
Be the first to start a discussion here.
Windows-1250
Windows-1250
Windows-1250
View on Wikipedia
from Wikipedia
Windows-1250
MIME / IANAwindows-1250
Alias(es)cp1250 (Code page 1250)
LanguagesCzech, Polish, Slovak, Hungarian, Slovene, Serbo-Croatian (Latin script), Montenegrin, Romanian (before 1993 spelling reform), Turkmen, Rotokas, Albanian, English, German, Irish, Luxembourgish, Dutch
Created byMicrosoft
StandardWHATWG Encoding Standard
Classificationextended ASCII, Windows-125x
Other related encodingISO-8859-2

Windows-1250 is a code page used under Microsoft Windows to represent texts in Central European and Eastern European languages that use the Latin script. It is primarily used by Czech.[1] It is also used for Polish (as can Windows-1257), Slovak, Hungarian, Slovene (as can Windows-1257), Serbo-Croatian (Latin script), Romanian (before a 1993 spelling reform) and Albanian (as can Windows-1252). It may also be used with the German language, though it is missing uppercase ẞ.[a] German-language texts encoded with Windows-1250 and Windows-1252 are identical.

This has been replaced by UTF-8 far more than Windows-1252 has. As of March 2025, less than 0.05% of all web pages use Windows-1250.[2][3][4]

Windows-1250 is similar to ISO-8859-2 and has all the printable characters it has and more. However, a few of them are rearranged (unlike Windows-1252, which keeps all printable characters from ISO-8859-1 in the same place). Most of the rearrangements seem to have been done to keep characters shared with Windows-1252 in the same place but three of the characters moved (Ą, Ľ, ź) cannot be explained this way, since those do not occur in Windows-1252 and could have been put in the same positions as in ISO-8859-2 if ˇ had been put e.g. at 9F.

IBM uses code page 1250 (CCSID 1250 and euro sign extended CCSID 5346) for Windows-1250.[5][6][7][8][9][10][11]

Character set

[edit]

The following table shows Windows-1250. Each character is shown with its Unicode equivalent.

Windows-1250[12]
0 1 2 3 4 5 6 7 8 9 A B C D E F
0x NUL SOH STX ETX EOT ENQ ACK BEL BS HT LF VT FF CR SO SI
1x DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US
2x  SP  ! " # $ % & ' ( ) * + , - . /
3x 0 1 2 3 4 5 6 7 8 9 : ; < = > ?
4x @ A B C D E F G H I J K L M N O
5x P Q R S T U V W X Y Z [ \ ] ^ _
6x ` a b c d e f g h i j k l m n o
7x p q r s t u v w x y z { | } ~ DEL
8x € ‚ „ … † ‡ ‰ Š ‹ Ś Ť Ž Ź
9x ‘ ’ “ ” • – — ™ š › ś ť ž ź
Ax NBSP ˇ ˘ Ł ¤ Ą ¦ § ¨ © Ş « ¬ SHY ® Ż
Bx ° ± ˛ ł ´ µ · ¸ ą ş » Ľ ˝ ľ ż
Cx Ŕ Á Â Ă Ä Ĺ Ć Ç Č É Ę Ë Ě Í Î Ď
Dx Đ Ń Ň Ó Ô Ő Ö × Ř Ů Ú Ű Ü Ý Ţ ß
Ex ŕ á â ă ä ĺ ć ç č é ę ë ě í î ď
Fx đ ń ň ó ô ő ö ÷ ř ů ú ű ü ý ţ ˙
  Different from ISO-8859-2
  Different from Windows-1252 to match ISO-8859-2
  Different from both Windows-1252 and ISO-8859-2

See also

[edit]

Notes

[edit]

References

[edit]
[edit]
Revisions and contributorsEdit on WikipediaRead on Wikipedia

Windows-1250

View on Grokipedia
from Grokipedia
Windows-1250 is a single-byte (SBCS) developed by for representing text in Central and Eastern European languages that use the , such as Polish, Czech, Slovak, Hungarian, Slovene, Croatian, Serbian (in ), and Romanian. It serves as 1250 in Windows environments, mapping 256 code points (0–255) to characters while maintaining compatibility with ASCII in the lower range (0–127). Also referred to as ANSI Central European or Central European (Windows), this encoding was introduced to support multilingual text in early Windows versions, including Windows 3.1, Windows 95, and Windows NT. It was formally registered with the Internet Assigned Numbers Authority (IANA) on May 3, 1996, under the MIME name "windows-1250." The encoding supports 223 printable characters, focusing on diacritics and symbols essential for the targeted languages, and is part of the broader Windows-125x family of code pages designed for regional text handling. While Windows-1250 provided an efficient solution for 8-bit text storage and display in legacy systems, its limitations—such as support for only 256 characters—have been largely superseded by , which enables broader multilingual capabilities in a single encoding standard. Detailed mappings and specifications are documented in Microsoft's resources and IANA registries for in and data processing.

Introduction

Overview

Windows-1250 is an 8-bit, single-byte standard, designated as 1250 by , that maps 256 distinct code points to characters, with the initial 128 code points identical to those in the ASCII standard for basic Latin letters, digits, and symbols. This design ensures backward compatibility with ASCII while extending support to additional glyphs required for regional scripts. Developed as part of Microsoft's efforts to internationalize the Windows operating system, Windows-1250 was introduced in the to accommodate Central and Eastern European languages that employ the Latin alphabet augmented with diacritical marks and special characters. It primarily serves languages such as Polish, Czech, Slovak, Hungarian, Slovene, Croatian, Serbian (in ), and Romanian, enabling proper representation of their native texts in software and documents. As a member of the Windows-12xx family of code pages—intended for non-East Asian scripts—Windows-1250 parallels encodings like , which targets Western European languages, but focuses on the unique orthographic needs of its designated region.

Purpose and Scope

Windows-1250 was designed to provide an efficient single-byte encoding scheme for Central European languages within Windows applications, addressing the limitations of ASCII and early ISO standards that lacked sufficient support for accented characters in these languages. The scope of Windows-1250 is limited to a total of 256 characters, prioritizing Latin-based scripts with common diacritics required for languages such as Polish, Czech, Slovak, and Hungarian; it does not support non-Latin scripts like Cyrillic or Greek, which are instead covered by other code pages such as Windows-1251. This encoding is optimized for text processing in Windows environments, with a strong emphasis on compatibility for file input/output operations and display in regional settings to ensure seamless handling of legacy applications. Compared to ASCII, Windows-1250 maintains full compatibility in the 0x00–0x7F range while extending the 0x80–0xFF byte values to include accented letters and symbols essential for the target Central European languages.

History and Development

Origins in Microsoft Code Pages

Windows-1250 was developed by in the early 1990s as part of the internationalization efforts for , which was released in April 1992, to support Central and Eastern European languages using the , such as Czech, Hungarian, Polish, and Slovak. This built upon earlier OEM code pages like CP852, which had been used in DOS and environments for similar linguistic regions, by extending the character repertoire to better accommodate Windows-specific needs while maintaining compatibility with legacy systems. Introduced in non-English versions of and Windows for Workgroups 3.11, it represented a shift toward region-specific encodings in 's ecosystem, diverging from the single ANSI used in the English edition. The drew influences from extensions to the ISO 646 standard and early drafts of ISO/IEC 8859-2 (Latin-2), but customized it for optimal integration with Windows font rendering technologies, including the newly introduced fonts in , which enabled scalable for accented characters common in Central European languages. Unlike strict adherence to international standards, these adaptations prioritized practical usability in Windows applications, such as improved support for diacritics and punctuation in graphical user interfaces. First prominently documented in 1993 alongside , it was named "Windows Central European" to highlight its regional focus and distinguish it from ANSI-compliant alternatives. As part of the broader Windows-125x series of single-byte code pages—where the "1250" designation specifically denotes Central European coverage—Windows-1250 contrasted with , which targeted Western European languages. This series emerged from Microsoft's need to provide localized text handling without relying solely on emerging standards, ensuring while expanding global reach in the pre-Windows 95 era.

Standardization and Evolution

Windows-1250 was formally documented and registered with the (IANA) in 1996 as the MIME charset name "windows-1250," enabling its use in internet protocols and standards. Following its initial development in the , Windows-1250 underwent minor updates, particularly in , when released a euro symbol (€) addition for code pages including 1250 to support the upcoming introduction of the currency; this update was integrated into service packs and later extended to and 98 for improved compatibility with Central European fonts and symbols. The encoding has seen no major revisions since its inception, remaining largely stable under Microsoft's proprietary control, which allowed for tweaks diverging from international standards like ISO/IEC 8859-2, such as the addition of characters for better Windows font rendering. With the release of in 2001, Microsoft began emphasizing (UTF-16 internally) for new applications, marking the start of deprecation trends for legacy code pages like Windows-1250, though full support persisted for backward compatibility in non-Unicode programs. By the 2010s, explicitly recommended over code pages for consistent in Windows applications, as outlined in developer guidelines promoting to avoid locale-specific inconsistencies. Despite this shift, Windows-1250 continues to serve as the default ANSI for Central European locales (e.g., Polish, Czech) in Windows as of 2025, ensuring legacy software compatibility while encouraging migration to via system settings.

Technical Specifications

Encoding Structure

Windows-1250 is an 8-bit single-byte scheme that defines a total of 256 code points, corresponding to byte values from 0x00 to 0xFF in notation. This fixed structure allows for straightforward mapping of characters to bytes, making it suitable for legacy systems where processing efficiency was paramount. The encoding is designed as a superset of the 7-bit US-ASCII standard, ensuring compatibility with basic Latin text and control characters. The code point allocation divides the 256 slots into two primary ranges: bytes 0x00 through 0x7F, which align directly with ASCII for control characters (such as 0x00 for null and 0x1F for unit separator) and printable basic Latin characters (from 0x20 space to 0x7E tilde), and bytes 0x80 through 0xFF, reserved for language-specific extensions primarily targeting Central and Eastern European scripts using the Latin alphabet. This bifurcation maintains interoperability with ASCII-based systems while providing room for additional glyphs, such as accented letters and diacritics, without altering the foundational 128-character set. As a single-byte encoding, Windows-1250 represents each character with exactly one 8-bit byte, eschewing multi-byte sequences found in more complex schemes like ; this fixed-width design simplifies parsing and rendering in early computing environments, where variable-length encodings could introduce overhead in string manipulation and display routines. A notable feature is its deviation from ISO standards, particularly in the 0x80–0x9F range, where control codes in ISO/IEC 8859-2 are reassigned to printable characters—for instance, 0x8A maps to the uppercase (S with )—to better accommodate practical needs in Windows applications. Unlike Unicode-based encodings, Windows-1250 requires no byte-order mark (BOM) for interpretation, as its single-byte format renders byte order and concerns irrelevant; text streams in this encoding can thus be processed directly without preamble indicators.

Byte Values and Assignment

Windows-1250 employs an 8-bit structure where the byte values 0x00 through 0x7F directly correspond to the ASCII standard, ensuring compatibility with basic Latin text. Bytes 0x00 to 0x1F are assigned to s identical to those in ASCII, such as 0x00 for NULL and 0x0A for line feed. Bytes 0x20 to 0x7E map to the printable ASCII characters, including 0x20 for space and 0x7A for lowercase 'z'. The byte 0x7F is designated for the delete . In the extended range of 0x80 to 0xFF, Windows-1250 assigns 123 characters (all printable), primarily supporting Central European scripts through Latin letters with modifications and typographic symbols. Notably, 27 positions within 0x80 to 0x9F are redefined from the C1 control codes used in or to printable characters, such as 0x82 for the single low-9 quotation mark (U+201A) and 0x8D for the Latin capital letter T with caron (U+0164). Five bytes in this subrange—0x81, 0x83, 0x88, 0x90, and 0x98—remain undefined. The assignments in 0xA0 to 0xBF focus on spacing characters, diacritical marks, and uppercase letters with accents, exemplified by 0xA0 for the (U+00A0) and 0xA1 for the (U+02C7). The range 0xC0 to 0xFF predominantly covers uppercase and lowercase letters with various accents along with additional symbols, such as 0xC0 for the Latin capital letter R with acute (U+0154) and 0xFF for the dot above (U+02D9). These mappings enable representation of characters unique to languages like Polish, Czech, and Hungarian.
Byte RangeDescription of AssignmentsExamples
0x00–0x1FASCII control characters0x00: NULL (U+0000), 0x09: Horizontal tab (U+0009)
0x20–0x7EPrintable ASCII characters0x21: (!, U+0021), 0x41: Latin capital letter A (A, U+0041)
0x7FDelete control0x7F: Delete (U+007F)
0x80–0x9FTypographic symbols, letters with carons/acutes, and undefined positions (27 redefined from controls)0x82: Single low-9 quotation mark (‚, U+201A), 0x91: Left single quotation mark (‘, U+2018), 0x9A: Latin small letter s with (š, U+0161)
0xA0–0xBFNon-breaking space, diacritics, and accented uppercase0xA0: ( , U+00A0), 0xA2: (˘, U+02D8), 0xA3: Latin capital letter L with (Ł, U+0141), 0xAF: Latin capital letter Z with dot above (Ż, U+017B)
0xC0–0xFFAccented uppercase and lowercase letters, additional symbols0xC0: Latin capital letter R with acute (Ŕ, U+0154), 0xE0: Latin small letter r with acute (ŕ, U+0155), 0xFF: Dot above (˙, U+02D9)

Character Coverage

Basic Latin and Punctuation

The Basic Latin and range in Windows-1250 corresponds to byte values 0x00 through 0x7F, encompassing 128 characters that form the core of the encoding. This range is defined identically to the US-ASCII standard, ensuring backward compatibility with systems and software designed for 7-bit ASCII text processing. As a single-byte encoding, Windows-1250 assigns these bytes directly to characters without alteration, facilitating the representation of basic English-language content in international contexts. The printable characters within this range include the 26 uppercase letters (A–Z, bytes 0x41–0x5A), 26 lowercase letters (a–z, bytes 0x61–0x7A), and the 10 digits (0–9, bytes 0x30–0x39). Common punctuation and symbols, such as the (!) at 0x21, quotation marks (" and ') at 0x22 and 0x27, (#) at 0x23, ($) at 0x24, (%) at 0x25, (&) at 0x26, apostrophe ('), parentheses ( and ) at 0x28–0x29, (*) at 0x2A, plus (+) at 0x2B, (,) at 0x2C, (-) at 0x2D, period (.) at 0x2E, slash (/) at 0x2F, colon (:) at 0x3A, (;) at 0x3B, less-than (<) and greater-than (>) at 0x3C–0x3E, (?) at 0x3F, (@) at 0x40, square brackets [ and ] at 0x5B–0x5D, () at 0x5C, (^) at 0x5E, (_) at 0x5F, (`) at 0x60, curly braces { and } at 0x7B–0x7D, (|) at 0x7C, and (~) at 0x7E, provide essential tools for sentence structure, , and formatting in text. Additionally, the character at 0x20 serves as a fundamental . Control characters occupy bytes 0x00–0x1F and 0x7F, supporting non-printable functions critical for data interchange and display. Notable examples include the (NUL) at 0x00 for string termination, line feed (LF) at 0x0A for vertical spacing in Unix-style line endings, carriage return (CR) at 0x0D for horizontal positioning in DOS-style endings, horizontal tab (HT) at 0x09 for columnar alignment, and (DEL) at 0x7F for erasing positions in teletype operations. These controls enable consistent text formatting across files, terminals, and protocols, underpinning the reliability of Windows-1250 in mixed-language environments. By mirroring US-ASCII in this foundational block, Windows-1250 supports the seamless integration of English terminology and symbols into documents primarily using Central European scripts, promoting without requiring translation for basic elements.

Central European Extensions

Windows-1250 extends the Basic Latin and punctuation characters of the ASCII standard by incorporating approximately 128 additional code points in the range 0x80–0xFF to support the diverse Latin-based scripts of . Of these, several code points (0x81, 0x83, 0x88, 0x8D, 0x8F, 0x90, 0x98) are undefined. These extensions focus on accented letters and diacritics essential for accurate representation of regional orthographies, enabling proper rendering of text in multiple languages without resorting to or other multi-byte encodings in legacy Windows environments. The character set includes key uppercase accented letters such as Á, Č, Ď, É, Ě, Í, Ň, Ó, Ř, Š, Ť, Ú, Ů, Ý, and Ž, along with their lowercase counterparts á, č, ď, é, ě, í, ň, ó, ř, š, ť, ú, ů, ý, and ž. These characters are grouped primarily by case, with uppercase forms concentrated in the 0xC0–0xDF range and lowercase in 0xE0–0xFF, while symbols and diacritic variants are interspersed in the 0x80–0xBF blocks for compatibility with existing software layouts. Coverage is tailored to several languages, including Polish with characters like Ł and ł for the unique "w" sound, Czech and Slovak featuring ř and ů for specific phonetic distinctions, and Hungarian incorporating ő and ű for rounded vowels. Other supported scripts include Croatian, Romanian, Serbian (Latin), and Slovenian, encompassing a total of about 100 extensions that prioritize Latin alphabet variations over non-Latin scripts. This selection ensures comprehensive support for everyday text in these regions, such as , , and official documents. Unique to Windows-1250 among early code pages are typographic elements like single low-9 ‚, double low-9 „, en dash –, and em dash —, which facilitate professional in European publications. Unlike Western European code pages such as , these extensions initially omitted the symbol € (added later at 0x80 via Windows updates in the late 1990s), emphasizing instead regional linguistic needs over pan-European currency adoption at the time of original design.

Compatibility and Mappings

Relation to ISO/IEC 8859-2

Windows-1250 and ISO/IEC 8859-2 are both single-byte character encodings primarily designed to support Central and Eastern European languages that use Latin-based scripts with diacritical marks, such as Polish, Czech, Slovak, Hungarian, and Croatian. Windows-1250 includes all the printable characters of ISO/IEC 8859-2 plus additional ones, but a few are rearranged, including key diacritics like acute accents, s, and ogoneks. For instance, the character Š (Latin capital letter S with , U+0160) appears in both encodings but is mapped to byte 0xA9 in ISO/IEC 8859-2 and 0x8A in Windows-1250. Specific rearrangements include Ą, Ľ, and ź. A significant structural difference arises in the byte range 0x80–0x9F, which ISO/IEC 8859-2 reserves for non-printable C1 control codes, such as line tabulation set (0x8A) and single shift two (0x8E), to maintain compatibility with international standards for interchange. In contrast, Windows-1250 repurposes 27 of these 32 slots—leaving five undefined, similar to other —for printable characters tailored to graphical user interfaces, including typographic symbols like the en dash (– at 0x96), em dash (— at 0x97), and additional diacritics such as (Latin capital letter Z with , U+017D at 0x8E). This redefinition enhances support for common punctuation and quotes in Windows applications but introduces incompatibilities with pure ISO-compliant systems. Beyond the C1 range, Windows-1250 adds unique glyphs not present in the standard, such as the euro sign (€ at 0x80) and single angle quotation marks (‹ at 0x8B and › at 0x9B, U+2039 and U+203A). While Windows-1250 includes all core printable characters from ISO/IEC 8859-2, the positional shifts for a few characters mean it is not a strict superset; direct byte-to-byte conversion can result in for mismatched characters. A few characters, such as Ľ (Latin capital letter L with , U+013D at 0xA5 in ISO/IEC 8859-2 versus 0xBC in Windows-1250), require explicit remapping during conversion to preserve fidelity. The (IANA) maintains them as distinct registered character sets, underscoring their non-interchangeability without transformation. Historically, the divergence traces to ISO/IEC 8859-2's finalization as an in 1987, aimed at uniform encoding across diverse systems. Windows-1250 emerged in 1992 as part of Microsoft Windows 3.1, positioned as a "Windows Latin-2" variant with optimizations for the operating system's text rendering and localization needs, including the printable C1 extensions to better accommodate UI elements like dialog boxes and menus. This evolution reflects 's proprietary adaptations for enhanced usability in regional Windows deployments, finalized around 1993.

Unicode Conversion Guidelines

Windows-1250 provides a direct one-to-one mapping for its defined characters to code points, primarily utilizing the (U+0080 to U+00FF) for accented Latin letters and the block (U+0100 to U+017F) for additional Central European extensions such as and rings. For instance, the byte 0xC1 maps to U+00C1 (LATIN CAPITAL LETTER A WITH ACUTE), while 0x8A maps to U+0160 (LATIN CAPITAL LETTER S WITH ). This structure ensures that the 251 printable characters in Windows-1250, including ASCII-compatible bytes from 0x00 to 0x7F, correspond uniquely to scalars without overlap or ambiguity. Converting from Windows-1250 to Unicode involves addressing the code page's Windows-specific additions, such as mappings for characters like 0xA5 (Š, U+0160) that extend beyond basic Latin sets, but these pose no significant challenges since all 251 defined characters (with 5 undefined bytes like 0x81) map losslessly to . There are no lossy conversions required, as Windows-1250 is a strict of Unicode's Basic Multilingual Plane, allowing full preservation of the original data during transformation. Round-trip compatibility is complete: encoding a Unicode string back to Windows-1250 and then to Unicode recovers the exact original, provided only supported characters are used. Practical guidelines for conversion emphasize using established APIs and detection methods. In Windows environments, the MultiByteToWideChar function with the identifier 1250 converts Windows-1250 bytes to UTF-16 wide characters, handling the mapping automatically for strings or buffers. To detect Windows-1250 encoding in files or streams lacking a byte-order mark (BOM), rely on heuristics such as the presence of bytes in the 0x80–0xFF range typical of Central European text, combined with validation against known invalid sequences. For web applications or modern interoperability, convert to as the target encoding, which supports seamless display and transmission of these characters across platforms. These extensions build on the Central European character coverage to ensure accurate representation of diacritics in languages like Polish and Czech.

Usage and Applications

In Windows Operating Systems

Windows-1250 serves as the default ANSI for Central European locales, such as Czech, Hungarian, Polish, Slovak, and Slovenian, in Windows operating systems from through Windows 11. In these locales, it is used by applications like for saving and opening text files in ANSI format and by Windows Explorer for handling non-Unicode file names, ensuring compatibility with legacy text-based operations. The encoding is integrated into Windows through the Code Page APIs, identifiable by the constant CP1250 (value 1250), which allows developers to convert between Windows-1250 and strings using functions like MultiByteToWideChar and WideCharToMultiByte. Font support is provided by system fonts such as CE (Central European variant) and Tahoma, which include glyphs for the extended Latin characters defined in Windows-1250. Users can switch code pages via regional settings in the Control Panel, under the non- language options, to accommodate different locales without reinstalling the OS. In early Windows versions, such as , Windows-1250 was essential for maintaining compatibility with applications using OEM 852, bridging the gap between console and graphical interfaces. However, starting with , shifted internal string storage to UTF-16 (initially UCS-2), deprecating code pages like Windows-1250 for core system operations while retaining them for legacy support. As of 2025, Windows-1250 remains available in the Win32 API for backward-compatible applications, though documentation strongly recommends migrating to to avoid encoding limitations and ensure global compatibility.

In Web and Legacy Software

Windows-1250 is declared as the character encoding in HTML documents using the <meta charset="windows-1250"> tag, allowing browsers to correctly interpret text content for Central and Eastern European languages. This declaration ensures proper rendering of characters such as accented letters in Polish, Czech, and Hungarian. Modern web browsers, including Google Chrome and Microsoft Edge, provide support for Windows-1250 primarily to handle legacy websites, decoding pages that specify this encoding via HTTP headers or meta tags. The official IANA MIME name for this encoding is "windows-1250", which is used in HTTP Content-Type headers like text/html; charset=windows-1250 to signal the encoding to clients. In legacy software from the and , Windows-1250 was commonly employed in applications targeting Central and Eastern European users, including older email clients that processed messages with regional diacritics and databases such as pre-Unicode versions of , which supported it as the WE8MSWIN1250 character set for storing and retrieving text data. Mis-detection of this encoding in such systems often results in , where bytes are misinterpreted as another charset like , leading to garbled displays of characters such as "ł" appearing as "£". As of 2025, Windows-1250 is rarely used in new due to the dominance of , which accounts for over 97% of websites, while Windows-1250 appears on less than 0.1% of sites with known encodings. However, it persists in some Eastern European government and enterprise systems for with legacy data and applications. The W3C recommends against specifying legacy encodings like Windows-1250 in HTTP headers for new content, favoring to ensure universal interoperability. In environments, tools such as iconv facilitate conversions involving Windows-1250, for example, using the command iconv -f WINDOWS-1250 -t UTF-8 input.txt > output.txt to migrate legacy files to modern standards.

References

  1. https://learn.microsoft.com/en-us/openspecs/windows_protocols/ms-ucoderef/28fefe92-d66c-4b03-90a9-97b473223d43
  2. https://www.iana.org/assignments/charset-reg/windows-1250
  3. https://learn.microsoft.com/en-us/windows/win32/intl/code-page-identifiers
  4. https://learn.microsoft.com/en-us/globalization/encoding/encoding-overview
  5. https://learn.microsoft.com/en-us/windows/win32/intl/code-pages
  6. https://www.os2museum.com/wp/where-did-cp852-come-from/
  7. https://www.aivosto.com/articles/charsets-codepages-windows.html
  8. https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page
  9. http://www.columbia.edu/kermit/cp1250.html
  10. https://www.unicode.org/Public/MAPPINGS/VENDORS/MICSFT/WINDOWS/CP1250.TXT
  11. https://encoding.spec.whatwg.org/#windows-1250
  12. https://learn.microsoft.com/en-us/typography/opentype/otspec183/euro
  13. https://www.fileformat.info/info/charset/windows-1250/list.htm
  14. https://www.fileformat.info/info/charset/ISO-8859-2/list.htm
  15. https://www.iana.org/assignments/character-sets
  16. https://www.iso.org/standard/16339.html
  17. https://www.compart.com/en/unicode/charsets/windows-1250
  18. https://learn.microsoft.com/en-us/windows/win32/api/stringapiset/nf-stringapiset-multibytetowidechar
  19. https://unicode-org.github.io/icu/userguide/conversion/detection.html
  20. https://stackoverflow.com/questions/3864240/default-code-page-for-each-language-version-of-windows
  21. https://superuser.com/questions/670197/finding-out-the-default-character-encoding-in-windows
  22. https://learn.microsoft.com/en-us/typography/font-list/arial
  23. https://stackoverflow.com/questions/66072117/why-does-windows-use-utf-16le
  24. https://www.w3.org/International/O-charset-lang.html
  25. https://chromium.googlesource.com/chromium/%2B/refs/heads/trunk/chrome/browser/character_encoding.cc
  26. https://hsivonen.fi/chardetng/
  27. https://w3techs.com/technologies/details/en-windows1250
  28. https://www.w3.org/International/docs/encoding/
Add your contribution
Related Hubs
User Avatar
No comments yet.