Existing users, 
 EncodingMaster - 1.6.1text encodings tool: convert, verify & more |
|
||||||||||||||||
|
|||||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
Instantly fixes entire Web-site's hidden text encoding! 
- Version: 1.11, 10/4/2005 12:49PM PST
info630
EncodingMaster is an excellent software tool which even boasts BATCH-PROCESSING! I am using it to convert entire folders of numerous UTF-16 text files (exported as complex HTML from FileMaker Pro 7) into UTF-8 files.
FMPro7 can export "text field contents" (as opposed to records) ONLY as UTF-16, which normally prevents users from using the client-level FMPro 7 as a broadly-compatible Web-site generator or host unless they upgrade to the FMPro Server versions ($1K+). EncodingMaster fixes this UTF-16 problem.
Note that including a HTML meta-tag specifying a "charset" DOES NOT by itself make a Web page readable correctly by a client browser. The invisible code "under" the HTML text may still contain conflicting Windows, Mac, or language-specific code that the browser (or Google's indexing and cached files!) can't display correctly. It takes an industrial-strength text-utility like EncodingMaster to correct the problem -- hopefully by batch-processing your whole Web-site.
Suggestions: The author might consider an "Advanced" setting in EncodingMaster to permit users to convert their ORIGINAL text files (instead of the admittedly safer "Save a Copy" default). In my case. all my original data resides in the FMPro database, so the exported HTML text files are easily replaced. Another option would be a user-definable target folder/path for saving converted files. Also useful would be for the program to retain the user's favorite conversion-settings as named, reloadable configuration files.
FMPro7 can export "text field contents" (as opposed to records) ONLY as UTF-16, which normally prevents users from using the client-level FMPro 7 as a broadly-compatible Web-site generator or host unless they upgrade to the FMPro Server versions ($1K+). EncodingMaster fixes this UTF-16 problem.
Note that including a HTML meta-tag specifying a "charset" DOES NOT by itself make a Web page readable correctly by a client browser. The invisible code "under" the HTML text may still contain conflicting Windows, Mac, or language-specific code that the browser (or Google's indexing and cached files!) can't display correctly. It takes an industrial-strength text-utility like EncodingMaster to correct the problem -- hopefully by batch-processing your whole Web-site.
Suggestions: The author might consider an "Advanced" setting in EncodingMaster to permit users to convert their ORIGINAL text files (instead of the admittedly safer "Save a Copy" default). In my case. all my original data resides in the FMPro database, so the exported HTML text files are easily replaced. Another option would be a user-definable target folder/path for saving converted files. Also useful would be for the program to retain the user's favorite conversion-settings as named, reloadable configuration files.
Most Recent Replies: View All 2 Replies
- Instantly fixes entire Web-site's hidden text encoding!
But what does it do? Pretty much the same as my text editor when I tell my text editor to save a utf-16 file to utf-8: NOT MUCH AT ALL. I have some multilanguaged files to convert from UTF-16 to UTF-8. EncodingMaster did not help me - all special chars were garbled, no qualitative conversion was made, just a chop-off of the 2bytes to one byte.
Yes, I can save my files in utf-8 via EM and later on fix the files with UnicodeChecker, but that does not make life easy.
As well, I converted a file with EM from utf16 to utf8 and the resulting file was BIGGER that the original. Hmm...