Re: Integration of Guilev2 branches into master

I /think/ it is Unicode in NTFS now, but UCS/UTF-16 and not UTF-8: https://stackoverflow.com/questions/2050973/what-encoding-are-filenames-in-ntfs-stored-as https://en.wikipedia.org/wiki/Universal_Coded_Character_Set#Relationship_with_Unicode Joram

Re: Integration of Guilev2 branches into master

On 2/10/2020 3:22 PM, Han-Wen Nienhuys wrote: How are filenames encoded on Windows? Not sure which Microsoft document is authoritative, but... " NTFS stores file names in Unicode. In contrast, the older FAT12, FAT16, and FAT32 file systems use the OEM character set. "

Re: Integration of Guilev2 branches into master

Am Mo., 10. Feb. 2020 um 22:43 Uhr schrieb David Kastrup : > > Han-Wen Nienhuys writes: > > > On Mon, Feb 10, 2020 at 9:44 PM Thomas Morley > >> (2) > >> A guile-2 build from current master is unable to find the file. > >> warning: cannot find file: `filename_?.ly' > >> fatal error: fail

Re: Integration of Guilev2 branches into master

Am Mo., 10. Feb. 2020 um 22:22 Uhr schrieb Han-Wen Nienhuys : > > > > On Mon, Feb 10, 2020 at 9:44 PM Thomas Morley > wrote: >> >> >> One is called 'filename.ly' the other 'filename_名字♯.ly' >> >> Observations >> (1) >> With 2.19.84 both files are found and compiled. >> 'filename_名字♯.ly' needs app

Re: Integration of Guilev2 branches into master

Han-Wen Nienhuys writes: > On Mon, Feb 10, 2020 at 9:44 PM Thomas Morley > wrote: > >> >> One is called 'filename.ly' the other 'filename_名字♯.ly >> ' >> >> Observations >> (1) >> With 2.19.84 both files are found and compiled. >> 'filename_名字♯.ly

Re: Integration of Guilev2 branches into master

On Mon, Feb 10, 2020 at 9:44 PM Thomas Morley wrote: > > One is called 'filename.ly' the other 'filename_名字♯.ly > ' > > Observations > (1) > With 2.19.84 both files are found and compiled. > 'filename_名字♯.ly ' needs app

Re: Integration of Guilev2 branches into master

Am Mo., 10. Feb. 2020 um 12:40 Uhr schrieb David Kastrup : > > Han-Wen Nienhuys writes: > > > On Sat, Feb 8, 2020 at 11:43 AM David Kastrup wrote: > > > >> Ok, there are still 3 unmerged patches marked XXX in the (now rebased) > >> branch dev/guile-v2-work . They are unmerged because they are ma

Re: Integration of Guilev2 branches into master

David Kastrup writes: > Han-Wen Nienhuys writes: > >> On Sat, Feb 8, 2020 at 11:43 AM David Kastrup wrote: >> >>> Ok, there are still 3 unmerged patches marked XXX in the (now rebased) >>> branch dev/guile-v2-work . They are unmerged because they are marked >>> XXX . Here is the list: > > Ah,

Re: Integration of Guilev2 branches into master

Han-Wen Nienhuys writes: > On Sat, Feb 8, 2020 at 11:43 AM David Kastrup wrote: > >> Ok, there are still 3 unmerged patches marked XXX in the (now rebased) >> branch dev/guile-v2-work . They are unmerged because they are marked >> XXX . Here is the list: >> > > can you push the branch? I can't

Re: Integration of Guilev2 branches into master

On Sat, Feb 8, 2020 at 11:43 AM David Kastrup wrote: > Ok, there are still 3 unmerged patches marked XXX in the (now rebased) > branch dev/guile-v2-work . They are unmerged because they are marked > XXX . Here is the list: > can you push the branch? I can't find some of the sha1s you mention.

Re: Integration of Guilev2 branches into master

David Kastrup writes: > David Kastrup writes: >> Han-Wen Nienhuys writes: >> >>> On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: >>> I propose that I am going to pick up the pieces of not-actually-formally-reviewed patches making up the bulk of them and put them, Guilev2-gua

Re: Integration of Guilev2 branches into master

David Kastrup writes: > Han-Wen Nienhuys writes: > >> On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: >> >>> I propose that I am going to pick up the pieces of >>> not-actually-formally-reviewed patches making up the bulk of them and >>> put them, Guilev2-guarded (so that they don't affect

Re: Integration of Guilev2 branches into master

Am Fr., 7. Feb. 2020 um 19:31 Uhr schrieb David Kastrup : > > Han-Wen Nienhuys writes: > > > On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: > > > >> I propose that I am going to pick up the pieces of > >> not-actually-formally-reviewed patches making up the bulk of them and > >> put them, Gu

Re: Integration of Guilev2 branches into master

Han-Wen Nienhuys writes: > On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: > >> I propose that I am going to pick up the pieces of >> not-actually-formally-reviewed patches making up the bulk of them and >> put them, Guilev2-guarded (so that they don't affect Guilev1 >> compilations) into st

Re: Integration of Guilev2 branches into master

Han-Wen Nienhuys writes: > On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: > >> I propose that I am going to pick up the pieces of >> not-actually-formally-reviewed patches making up the bulk of them and >> put them, Guilev2-guarded (so that they don't affect Guilev1 >> compilations) into st

Re: Integration of Guilev2 branches into master

Han-Wen Nienhuys writes: > On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: > >> I propose that I am going to pick up the pieces of >> not-actually-formally-reviewed patches making up the bulk of them and >> put them, Guilev2-guarded (so that they don't affect Guilev1 >> compilations) into st

Re: Integration of Guilev2 branches into master

On Fri, Feb 7, 2020 at 6:54 PM David Kastrup wrote: > I propose that I am going to pick up the pieces of > not-actually-formally-reviewed patches making up the bulk of them and > put them, Guilev2-guarded (so that they don't affect Guilev1 > compilations) into staging->master without going throug