#1
|
|||
|
|||
don't change the source code
I love the way that I can use URP as a web page editor. While not as powerful as a dedicated app like Dreamweaver, it's fast, and it can be done within the URP interface. Nice.
What's not so nice is that URP changes my source code, apparently based on assumptions that don't match my preferences. For instance, I prefer to have my HTML tags all lower case, e.g., <p>. When I save a webpage using URP, all tags are rendered upper case. Thus I have a cleanup job after working with URP. Please take a look at this and see if there is a way to get URP to not take the extra step of changing around my source code. Thanks. - Bal |
#3
|
|||
|
|||
OK - I know that Microsoft LOVES to assume it knows better than the user how things should be.
Wondering if there is any other editing alternative that could work with URP. That's obviously a business decision as well as a tech decision. Just a thought. As a work-around, I use NoteTab Pro and set up a clipbook macro that turns all HTML tags that I have identified into lower case. It basically means that I won't use URP for final product, though it's very good for touching things up. Thanks. - Bal |
#4
|
|||
|
|||
Tags in upper case actually break xhtml compliance -- Newer versions of MS Visual Studio, Expression Web, etc. default to putting tags in lower case and provide a compile warning if tags are in upper case. Older versions of Visual Studio (and tools like Visual Interdev) used MSHTML and would convert tags to upper-case, and also add <tbody> to tables, and other things like that which might cause the appearance of the document to change.
Often people will do like wordmuse is, and run the output of MSHTML through HTML Tidy, run a regex on it, or something else of that nature to get lower case tags. Some editors that use MSHTML will also wrap HTML Tidy for compliant output. Thanks, Mark (UR newbie - just bought and on the learning curve) |
|
|