python upon which pymailgui heavily depends it may be difficult for pythoncoded email clients to support some features better until python' libraries dotoo moreoverthe unicode support that is present in this program has been tested neither widely nor rigorously just like ' pyeditthis is currently still single-user system designed to work as book examplenot an open source project because of thatsome of the current unicode policies are partially heuristic in nature and may have to be honed with time and practice for exampleit may prove better in the end to use utf- encoding (or none at allfor sends in generalinstead of supporting some of the many user options which are included in this book for illustration purposes since utf- can represent most unicode code pointsit' broadly applicable more subtlywe might also consider propagating the main text part' unicode encoding to the embedded pyedit component in view and edit windowsso it can be used as known encoding by the pyedit save button as isusers can pop up the main text' part in view windows to save with known encoding automaticallybut saves of drafts for mails being edited fall back on pyedit' own unicode policies and gui prompts the ambiguous encoding for saved drafts may be unavoidablethough--users might enter characters from any character setboth while writing new mails from scratch and while editing the text of replies and forwards (just like headers in replies and forwardsthe initial known encoding of the original main text part may no longer apply after arbitrary editsin additionthere is no support for non-ascii encodings of full mail textit' not impossible that encoded text might appear in other contexts in rare emails ( in attachment filenameswhose undecoded form may or may not be valid on the receiving platform' filesystemand may require renaming if allowed at all)and although internationalization is supported for mail contentthe gui itself still uses english for its buttonslabelsand titles--something that truly locationneutral program may wish to address in other wordsif this program were to ever take the leap to commercial-grade or broadly used softwareits unicode story would probably have to be revisited also discussed in future release of the email package may solve some unicode issues automaticallythough pymailgui may also require updates for the solutionsas well as for incompatibilities introduced by them for nowthis will have to stand as useful object lesson in itselffor both better and worsesuch changes will always be fact of life in the constantly evolving world of software development and so on--because this software is open sourceit is also necessarily open-ended ultimatelywriting complete email client is substantial undertakingand we've taken this example as far as we can in this book to move pymailgui further alongwe' probably have to consider the suitability of both the underlying python ideas for improvement