Changes between Version 4 and Version 5 of UTF8Notes


Ignore:
Timestamp:
10/09/11 15:07:44 (8 years ago)
Author:
noz
Comment:

Added todo list

Legend:

Unmodified
Added
Removed
Modified
  • UTF8Notes

    v4 v5  
    4242 
    4343In reading the edit files, all strings are maintained in UTF-8 until needed. 
    44 Glyphs are read in directly to a wchar_t type. 
     44 
     45Glyphs are read in directly to a '''wchar_t''' type, using the "char" parse type, and the ''parser_getchar()'' function. This does not apply to preference files, where the symbols are all treated as '''int'''s. 
    4546 
    4647---- 
     
    7677=== Windows === 
    7778 
    78 Windows does not properly support UTF-8 using the standard C library routines for locale, so the ''term->mbcs_hook'' function is defined to use the Windows-native ''MultiByteToWideChar()'' function, and the external files are assumed to be in UTF-8. Wide chars from the canvas are written directly to the screen using ''ExtTextOutW()'' in ''Term_text_win()''. 
     79Windows does not properly support UTF-8 using the standard C library routines for locale, so the ''term->mbcs_hook'' function is defined to use the Windows-native ''!MultiByteToWideChar()'' function, and the external files are assumed to be in UTF-8. Wide chars from the canvas are written directly to the screen using ''ExtTextOutW()'' in ''Term_text_win()''. 
    7980 
    8081=== OSX === 
     
    8990 
    9091There are significant problems in adapting an Android port to this change, as the support for wide chars in older versions of Android is lacking. I understand that '''wchar_t''' is implemented as an 8-bit quantity, and some of the support functions such as ''mbstowcs()'' are missing, or broken. It may be possible to overload this using ''Term_mbstowcs()''. ''Please update this if you make any significant progress'' 
     92 
     93---- 
     94 
     95== To Do == 
     96 
     97Things still remaining to do: 
     98 
     99* Check screen dumps 
     100* Change display editor to allow arbitrary input of unicode chars / avoid scrolling display of chars? 
     101* Check preference files, and how they store chars. Check that display changes work. 
     102* Improve way that input key is matched to display char. Locale-aware input? 
     103* Change tile-handling, so that the tile index is the look up into the bitmap, and not (tile index & 0x7f) 
     104