BBTidy - 1.0b10BBEdit plugin that checks & corrects HTML/XML |
|
||||||||||||||
|
|||||||||||||||
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
Command line tool - Version: 1.0b10, 1/14/2004 12:42AM PST
(1 of 1 users found this comment useful)
Tidy for Mac OS
To respond to fuy :
>BBTidy rocks. It's an excellent complement to BBEdit's built-in syntax checker. Glad someone updated it at least somewhat -- the CLI version at tidy.sourceforge.net is rather ahead.
>
Thanks for the compliments.
The "someone" is me, the author of BBTidy.
Re the command line interface - I deliberately chose to release this version of BBTidy (which took me a while) based on the last version of the "Tidy Classic" source code. I intend to make all future versions of Tidy for Mac OS based on the newer "TidyLib" source code (which I help maintain) - it is possible I will change the user interface, and limit support to Mac OS X only, so obviously this is a decision I won't make lightly. I felt it best to have a dividing line in the versions of BBTidy.
Regards, Terry
BBTidy, BBEdit v7.1.x, and UTF-16 - Version: 1.0b10, 1/14/2004 12:34AM PST
(1 of 1 users found this comment useful)
Tidy for Mac OS
To respond to wildCardIV's comments :
>For some reason it will only output corrected code if the character encoding is set to UTF16. If I set it to anything else, UTF8, Latin1, anything, it outputs a blank page. It still outputs the error page with a list of all the things it "would" correct, but the output page is blank. I'm using BBEDIT 7.1.1.
>
If you read the section of documentation regarding support of multi-byte text you will see this is expected behaviour if your input document uses the UTF-16 "charset". During development I actually disabled all other character encoding choices in the popup menu when the input was UTF-16, expressively to prevent users from doing what you did; but in the end, I decided to leave the choice up to the user with the understanding that the wrong thing might happen if you selected a different character encoding from the popup menu. There are several ways to do something different with the character encoding if necessary, such as configuring BBEdit; changing the input document; and specifying separate input and output character encoding options in the "Other Config..." dialog.
It is entirely possible you found a bug (there are too many combinations to test, and I couldn't do a lot of testing with UTF-16 documents) - if so, I would be more than happy to work with you to solve the issue, and you should contact me via EMail.
Regards, Terry
Only UTF16 



- Version: 1.0b10, 1/8/2004 10:08AM PST
(1 of 1 users found this comment useful)
wildcardIV
For some reason it will only output corrected code if the character encoding is set to UTF16. If I set it to anything else, UTF8, Latin1, anything, it outputs a blank page. It still outputs the error page with a list of all the things it "would" correct, but the output page is blank. I'm using BBEDIT 7.1.1, Mac OS X 10.3.2 Server, Dual 1 Ghz MDD, 768 MB RAM.