Re^3: Odd encoding problem in Tk app when packaged with pp

I can't see this mentioned in the bug reports you linked, so I'm guessing you know this from personal experience...?

Yup, 99/100 PAR/pp questions are solved with -x, the rest are solved with -l, the rest are bugs :)

I linked the first bug reports I could find, didn't seem important to check if they mention pp -x

Comment on Re^3: Odd encoding problem in Tk app when packaged with pp

Replies are listed 'Best First'.
Re^4: Odd encoding problem in Tk app when packaged with pp by Anonymous Monk on Jan 28, 2013 at 11:59 UTC
I linked the first bug reports I could find, didn't seem important to check if they mention pp -x Because , with older versions of Tk, pp -x won't help, so you need latest Tk and pp -x	[reply]
Re^5: Odd encoding problem in Tk app when packaged with pp by elef (Friar) on Jan 28, 2013 at 12:28 UTC
Thanks for the additional info. I have Tk 804.029. Not technically the very latest version, but it's the latest available through ppm and clearly recent enough. (PAR::Packer is 1.013).	[reply]
Re^4: Odd encoding problem in Tk app when packaged with pp by elef (Friar) on Jan 28, 2013 at 12:17 UTC
Perhaps pp should display a warning when it's run without -x along the lines of "Attention, running without -x may generate an executable that runs without error messages but does not function fully correctly. -x is always strongly recommended." It would cut down on questions and bug reports.	[reply]
Re^5: Odd encoding problem in Tk app when packaged with pp by marto (Cardinal) on Jan 28, 2013 at 12:19 UTC
Why don't you suggest this to the maintainers?	[reply]