octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #58689] [MXE Octave] Update mesa to use meson


From: Markus Mützel
Subject: [Octave-bug-tracker] [bug #58689] [MXE Octave] Update mesa to use meson as (native) build tool
Date: Sun, 5 Jul 2020 06:12:14 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/83.0.4103.116 Safari/537.36 Edg/83.0.478.58

Update of bug #58689 (project octave):

                  Status:               Need Info => In Progress            

    _______________________________________________________

Follow-up Comment #5:

Thank you again for the update.
I'm not sure if this won't cause some issues though.
Other packages might chose to encode their files in UTF-8 (which might
arguably be a better choice).
Reading such files in Latin-1 might result in mojibake for non-ASCII
characters. That might not be a problem per se. But writing these strings back
to a file (without specifying the encoding) encodes that mojibake in UTF-8 and
results in a wrong file.
It's maybe good enough to read the files in Latin-1 and treat the read strings
more like "byte streams". When writing those "byte streams" back to files, the
encoding could be set to Latin-1 as well. That probably ensures that what we
write back to the files is what we read from the source (in a byte-wise
manner).

The attached updated patch does that.

A "real solution" might be to read and write byte streams from and to the
files. But that would probably require a few other changes. And I'm not sure
it is worth the effort...

I'll try updating build-python.mk to python3 next and see if that breaks
anything.

(file #49431)
    _______________________________________________________

Additional Item Attachment:

File name: py3scripts_v3.patch            Size:12 KB
    <https://savannah.gnu.org/file/py3scripts_v3.patch?file_id=49431>



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?58689>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]