I'm trying to see * *Computação Musical com Exemlplos em Pdhttps://sites.google.com/site/porres/Computa%C3%A7%C3%A3oMusicalemPd.zip?attredirects=0 Alexandre Porres tutorial on linux pd-extended, but I can't see the comments..
I try pd-extended 0.42.5 and 0.43.4 downloaded today (12 13 2012)
On windows pd-extended 0.43.4 I can see the comments..
I'm still looking at why tclpd is causing this problem. Did removing tclpd totally solve it for you? i.e.
sudo rm /usr/lib/pd-extended/startup/tclpd
.hc
On Dec 13, 2012, at 8:00 PM, Esteban Viveros wrote:
I'm trying to see Computação Musical com Exemlplos em Pd Alexandre Porres tutorial on linux pd-extended, but I can't see the comments..
I try pd-extended 0.42.5 and 0.43.4 downloaded today (12 13 2012)
On windows pd-extended 0.43.4 I can see the comments..
-- Esteban Viveros
(27) 8815 7170 (27) 3066 0359 (11) 95761 4125 (11) 2738 7868
www.bandpage.com/estebanviveros
https://www.facebook.com/estebanviveros.art
http://www.papodecompositor-es.blogspot.com.br/
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list
On 12/21/2012 17:39, Hans-Christoph Steiner wrote:
I'm still looking at why tclpd is causing this problem. Did removing tclpd totally solve it for you? i.e
i found that the cause for these problems is often some initialization of i18n support. e.g. i had some problems with pdgst, where initializing gstreamer would turn the decimal point to "," on a german locale -> all numbers sent from pd-core to pd-gui would then be misinterpreted.
a quick tests shows, that the problem seems indeed to be related (though different). $ LANG=C pd -lib tcllib path-with-ç-in-comments.pd works fine here, whereas $ LANG=C.UTF-8 pd -lib tcllib path-with-ç-in-comments.pd hides the comments (C.UTF-8 is my default locale)
hope this helps with hunting down the problem.
rgmaser IOhannes
On 12/21/2012 20:27, IOhannes m zmölnig wrote:
hope this helps with hunting down the problem.
i _guess_ that the problem is somehow related to doubly encoding an UTF8 string.
anyhow, the way i "solved" the problem in pdgst, was to set the current locale to "C" before initializing gstreamer, and then restoring the original locale. it's a bit hacky though.
fgadsr IOhannes
On Dec 21, 2012, at 2:29 PM, IOhannes m zmölnig wrote:
On 12/21/2012 20:27, IOhannes m zmölnig wrote:
hope this helps with hunting down the problem.
i _guess_ that the problem is somehow related to doubly encoding an UTF8 string.
anyhow, the way i "solved" the problem in pdgst, was to set the current locale to "C" before initializing gstreamer, and then restoring the original locale. it's a bit hacky though.
The same thing worked for tclpd. This leads me to believe that perhaps the issue is in Pd itself, that it is not somehow registering its locale properly. But I don't really know where to look.
.hc
On Dec 21, 2012, at 2:27 PM, IOhannes m zmölnig wrote:
On 12/21/2012 17:39, Hans-Christoph Steiner wrote:
I'm still looking at why tclpd is causing this problem. Did removing tclpd totally solve it for you? i.e
i found that the cause for these problems is often some initialization of i18n support. e.g. i had some problems with pdgst, where initializing gstreamer would turn the decimal point to "," on a german locale -> all numbers sent from pd-core to pd-gui would then be misinterpreted.
a quick tests shows, that the problem seems indeed to be related (though different). $ LANG=C pd -lib tcllib path-with-ç-in-comments.pd works fine here, whereas $ LANG=C.UTF-8 pd -lib tcllib path-with-ç-in-comments.pd hides the comments (C.UTF-8 is my default locale)
hope this helps with hunting down the problem.
yes, that is very helpful. I was at the point of having absolutely no idea... I'll take a look.
.hc