Michel Chouinard

Hi @komal-maru

You’re welcome.

I had some spare time and I will work on the others in my spare time also.

I’ve been coding in PHP since 1998, so long enough to know about the problems encountered when files are saved in UTF-8 with BOM. And, by the way, when it happen, I can tel you that it’s very noticeable. Usually, PHP parse the file but send the BOM ahead in a response so we end up with a header already send error message on development settings, so missing it is almost impossible, but probable with careless programmers.

Your plug-in is great! But deceiving in that it doesn’t check for the BOM, it trigger the unprintable character info for ALL characters out of the basic ASCII characters table in comments and in strings.

Look at it this way, WordPress is used in the entire world, WordPress encourage internationalisation, a great plug-in come to help theme developers to make things wright but the plug-in itself doesn’t support internationalisation. And, at the end i’m told to just disable the option, rather than a “It’s worth investigating the mater”….

Hey! English isn’t the sole language in the world! My english isn’t to bat but not good enough for pro work!!! So I do have to create my strings in French and have my PO file translated by someone better than me… And I’m certain that’s the case for almost all non native english speaking developers in the world.

So, until someone comes with a solution in a plug-in of the same type, I wont recommend any of them to colleagues. Sorry.

Ok for the hidden files, I’ll check if I can set a filter to the archiver app.

For the info on unprintable characters. I know that it’s just an info… But can you do something about it cause it’s an annoyance. ??

I could check the plugin code for that but I lack the time to do that.