[bug #30172] Converting strings lossy results to different strings than on OS X

[Richard Frith-Macdonald]

Update of bug #30172 (project gnustep):

                Severity:              3 - Normal => 1 - Wish               
              Item Group:                     Bug => Change Request         

    _______________________________________________________

Follow-up Comment #2:

I don't think we have a definition of what a lossy string should be (so we
used our own).  I agree it would be nice to have compatibility here, though
given that this is the first comment I recall on it in about a decade, it
can't be that people use lossy C string format much.
Perhaps you could provide some testcases to demonstrate the algorithm OSX
uses to convert a unicode string to a lossy C string (possible something as
crude as removing every non-ascii character) ... if so it should be easy to
change the code to be compatible.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?30172>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/