No problem man. Fought my share of charset issues in the past and have more waiting for me in near future (mostly dealing with email parsing and template injection)
So it works fine in windows-1252 but not in utf-8 (I'm assuming the defaults in fresh installs of Ubuntu/Apache/tomcat/lucee would be utf-8)?
I was expecting you to say the opposite ... Tgat the old server was dishing out utf8 and the new setup had been configured to be windows-1252 or some other ANSI variant.
Even though you're back operational .... You should still make sure all of your charset settings are in alignment. It's common for them to be inconsistent. I suspect you have mismatched settings somewhere.
Places to check off the top of my head:
- the actual encoding of the files on disk
- the charset settings in the app server (lucee in this case)
- HTTP content-type headers injected by your webserver (Apache/iis/nginx) or servlet container (tomcat)
- any content-type meta tags in the HTML that your app sends to the browser to interept
The HTTP content-type header in Apache is important so that js/css and other text files that aren't handled by lucee get served in the right charset.