[L2Ork-dev] non-standard characters in path

Jonathan Wilkes jon.w.wilkes at gmail.com
Tue Nov 19 21:11:12 EST 2019


On Tue, Nov 19, 2019 at 2:58 PM Iain Mott <mott at escuta.org> wrote:
>
> The parent patch can be loaded if done so from within Purrdata, however,
> I think (i'm no longer in Windows), it won't open if you try to launch
> Purrdata by double clicking on the parent. I opened an issue on the Git

I've got a potential fix building in the CI. I'll post on the issue
tracker when
it's ready to download.

-Jonathan

>
> Thanks, Iain
>
> Em 19/11/2019 16:45, Jonathan Wilkes escreveu:
> > On Tue, Nov 19, 2019 at 1:09 PM Iain Mott <mott at escuta.org> wrote:
> >> Ah. I found that it's easy to reproduce on a Windows 10 machine (my
> >> laptop has this) with purrdata 2.10. Please extract the attached file.
> >> There is a masterpatch.pd and a subpatch.pd file included in a directory
> >> called "pürdãtá". If you open the masterpatch.pd in Purrdata the
> >> embedded "subpatch" abstraction fails to load. If you rename the
> >> directory purrdata, it will.
> > I can reproduce.
> >
> > It's confusing to say the least-- we can easily load the parent patch
> > which of course uses
> > the same special-character-laden path as the child abstraction.
> >
> > It seems quite unlikely that the loader path for abstractions somehow does
> > an end-run around the windows path-handling algorithm. I'll investigate.
> >
> > -Jonathan
> >
> >> Here is a table of accents/characters that mostly covers Portuguese (and
> >> probably covers Spanish) and perhaps even Scandinavian languages:
> >>
> >> http://www.lsi.usp.br/~help/html/iso.html
> >>
> >> I'd also add to this the following two common characters: º and ª
> >>
> >> Cheers,
> >>
> >> Iain
> >>
> >>
> >> Em 19/11/2019 14:23, Jonathan Wilkes escreveu:
> >>> On Tue, Nov 19, 2019 at 12:03 PM Iain Mott <mott at escuta.org> wrote:
> >>>> Thanks Jonathan. The version that's being used is 2.9.0 and not 2.10.0
> >>>> which I see is now available. So that's great. I'll be able to
> >>>> reinstall
> >>>> and test this on the work machines tomorrow. Will let you know how it
> >>>> goes.
> >>> 2.9.0 was supposed to have already fixed this issue:
> >>>
> >>> "fixed bug handling certain encodings in filenames under Windows
> >>> (thanks to Alv_ro on the Pd Forum for reporting it)"
> >>>
> >>> https://github.com/jonwwilkes/purr-data/releases/2.9.0
> >>>
> >>> -Jonathan
> >>>
> >>>> All the best,
> >>>>
> >>>> Iain
> >>>>
> >>>> Em 19/11/2019 13:02, Jonathan Wilkes escreveu:
> >>>>> Just to be clear-- we already have a special code path hooked in for
> >>>>> Windows to handle filename issues like these. So if you are using
> >>>>> Purr Data version 2.10.0 this problem shouldn't be happening.
> >>>>>
> >>>>> -Jonathan
> >>>>>
> >>>>> On Tue, Nov 19, 2019 at 10:33 AM Jonathan Wilkes
> >>>>> <jon.w.wilkes at gmail.com> wrote:
> >>>>>> On Tue, Nov 19, 2019 at 9:21 AM Iain Mott <mott at escuta.org> wrote:
> >>>>>>> Dear developers,
> >>>>>>>
> >>>>>>> I've been presenting Pd/Purrdata to an introductory sound design
> >>>>>>> class
> >>>>>>> and students have been installing the software on their mainly
> >>>>>>> Windows
> >>>>>>> machines. A common problem that I'm encountering is that many of the
> >>>>>>> students have user names with non-standard characters such as
> >>>>>>> "João" and
> >>>>>>> "Márcia". While it's possible to change the user name at the login
> >>>>>>> level, the path remains unchanged after re-boot/login and
> >>>>>>> Pd/Purrdata
> >>>>>>> fails to load objects and abstractions (abstraction at least and
> >>>>>>> they
> >>>>>>> appear in red in the patches). There is apparently a way to
> >>>>>>> resolve the
> >>>>>>> path problem at the system level by making changes to registry
> >>>>>>> values
> >>>>>>> (I'm not a regular Windows user), however I do not wish to make such
> >>>>>>> changes on the machines of the students because there is a risk
> >>>>>>> that I
> >>>>>>> may damage the system if I make a mistake.
> >>>>>>>
> >>>>>>> As a workaround I've been creating a new user name on each
> >>>>>>> machine but
> >>>>>>> as such, the users can't access there other docs.
> >>>>>>>
> >>>>>>> Since other programs don't seem to have this problem, my
> >>>>>>> question is:
> >>>>>>> can non-standard characters such as á, à and ã be made
> >>>>>>> permissible in
> >>>>>>> paths for Purr Data?
> >>>>>> Iain,
> >>>>>>
> >>>>>> Can you post a very simple example patch (e.g., one or two objects)
> >>>>>> that
> >>>>>> shows this problem?
> >>>>>>
> >>>>>> https://git.purrdata.net/jwilkes/purr-data/issues
> >>>>>>
> >>>>>> There's a special code-path specifically for Windows to address
> >>>>>> this problem
> >>>>>> so I'm unsure why it's not working on your users' machines.
> >>>>>>
> >>>>>> -Jonathan
> >>>>>>
> >>>>>>> Thanks very much,
> >>>>>>>
> >>>>>>> Iain
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> L2Ork-dev mailing list
> >>>>>>> L2Ork-dev at disis.music.vt.edu
> >>>>>>> https://disis.music.vt.edu/listinfo/l2ork-dev
> >>>>> _______________________________________________
> >>>>> L2Ork-dev mailing list
> >>>>> L2Ork-dev at disis.music.vt.edu
> >>>>> https://disis.music.vt.edu/listinfo/l2ork-dev
> >>


More information about the L2Ork-dev mailing list