Auto Highlight Closing Tags

I recently upgraded my Mac and reinstalled the Adobe suite. Since working with Dreamweaver on my new maching I've realised that the code view no longer auto highlights closing tags (eg; divs, lists etc). On my old setup I simply clicked on a tag and it would automatically identify/highlight the close tag.
I'm aware of the process of highlighting parent tags etc manually. But it used to happen auto? There doesn't seem to be any specific option for this in the 'Highlighting' preferences either?
Any suggestions people?
Thanks in advance!!!

I don't recall DW ever doing this. Mine doesn't. Perhaps you had installed a 3rd party extension that provided this feature?
Nancy O.

Similar Messages

Dreamweaver CC 2014.1: Auto uppercase on " nobr " closeing tag showing " /NOBR " when using tag wrap shortcut.

Using the tag wrap shortcut (Command/Ctrl + T) works well. But, I've had to use <nobr> to wrap non-breaking text. This is useful for working on HTML emails and this always leaves the with uppercase letters in the ending tag like this, "</NOBR>".
I understand that the <nobr> tag is outdated but Email HTML usually forces us to write code like this frequently.
Any ideas why?
I'm using Adobe Dreamweaver CC 2014.1

It's curious. But I often do HTML emails and have never had (or felt the need) to use this antique tag. Can you substitute CSS's white-space:nowrap instead? Anyhow, why do you object to the uppercase closing tag? Esthetics?

Overlapping or no closing tag

Using DW6.
Trying to insert anything, a div tag or spry menu bar in the menu_bar , main or footer content areas, and the insertion jumps to the body tag and inserts above the outer container.
I clicked on highlight invalid code
Code is hightlighted as overlapping or no closing tag for outer, inner and header container only.
So right now I cannot make any insertions, I have closed and reopened with same results. I have also tried to insert manually but nothing shows, although I can create and edit new rules.
Thanks for helping
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<title>index</title>
<link href="styles/css_main.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="outer_container">   (highlighted)
<div id="inner_container">   (highlighted)
    <div id="header">(highlighted)
      
    </div> (highlighted)
<div id="red_bar">Helping Saint Louis Sleep Better Since 2000</div>
<div id="menu_bar">sdfgsdfg</div>
         <div id="main_content">Contnt for id "main_content" Goes Here</div>
         <div id="footer">Contvent for id "footer" Goes Here</div>
</div>   (highlighted)
</div>(highlighted)
</body>
</html>
@charset "utf-8";
.include_header {
font-size: 75px;
color: #CC0000;
text-align: center;
margin: 0px;
font-variant: normal;
padding-top: 0px;
padding-right: 55px;
padding-bottom: 0px;
padding-left: 0px;
font-style: normal;
text-transform: none;
font-weight: 900;
font-family: Pupcat;
border-top-style: none;
border-right-style: none;
border-bottom-style: none;
border-left-style: none;
border-top-color: #336699;
border-right-color: #336699;
border-bottom-color: #336699;
border-left-color: #336699;
.hampton_address {
list-style-type: none;
margin: 0px;
float: left;
padding-left: 250px;
font-weight: bold;
color: #333;
background-color: #FFF;
.hampton_address ul li {
list-style-type: none;
.mcree_address ul li {
list-style-type: none;
.mcree_address {
float: right;
padding-right: 300px;
font-weight: bold;
color: #333;
text-decoration: none;
list-style-type: none;
background-color: #FFF;
#outer_container {
background-image: url(../images/background/gradient59803139.png);
background-repeat: no-repeat;
background-position: 100% 100%;
margin: 0px;
padding: 0px;
overflow: hidden;
visibility: visible;
z-index: 0;
height: 100%;
width: 100%;
left: 8px;
top: 7px;
#inner_container {
background-color: #FFF;
margin: 0 auto;
padding: 0px;
height: auto;
width: 968px;
overflow: hidden;
/* [disabled]visibility: visible; */
border: thick double #336699;
color: #333;
#header {
background-color: #FFF;
width: 968px;
overflow: hidden;
height: 205px;
border-top-style: none;
border-right-style: none;
border-bottom-style: none;
border-left-style: none;
border-top-color: #336699;
border-right-color: #336699;
border-bottom-color: #336699;
border-left-color: #336699;
#menu_bar {
margin: 0px;
padding: 0px;
float: left;
width: 250px;
#red_bar {
font-family: "Comic Sans MS", cursive;
color: #FFF;
background-color: #F00;
height: 40px;
width: 968px;
font-size: 24px;
text-align: center;
border-top-style: solid;
border-right-style: solid;
border-bottom-style: solid;
border-left-style: solid;
border-top-color: #336699;
border-right-color: #336699;
border-bottom-color: #336699;
border-left-color: #336699;

<table width="986" background-color="FFF" cellspacing ="0" cellpadding="0">
<tr>
    <td><img src="./images/logo/bed_guy.gif" width="195" height="116" alt="bedguy logo" /></td>
    <td><div class="include_header">The BedGuy</div></td>
    <td><a href="#"><img src="./images/logo/logo_sticker.jpg" width="205" height="96" alt="shop saint louis" border="0" /></a> </td>
</tr>
</table>
<div class="hampton_address">
<ul>
    <li>6431 Hampton Ave</li>
    <li>Saint Louis, MO 63109</li>
    <li>314-678-9100</li>
</ul>
</div>
<div class="mcree_address">
<ul>
    <li>4666 McRee Ave</li>
    <li>Saint Louis, MO 63110</li>
    <li>314-772-9999</li>
</ul>
</div>

Matching opening and closing tags in MXML

Is possible to match the opening and closing tag in MXML with Flash Builder 4.x?
In AS3 you can see the curly braces highlighted and you can type Ctrl+Shift+P to jump from one bracket to the other.
In DreamWeaver you can see the hierarchy for every HTML element, and you can click any HTML element to highlight the block inside.
I can see only icons with - and + for contract or expand the MXML blocks, but they are working wrong !

If you click the element in Outline view, it should highlight the entire tag for you. Is it not doing this in FB 4?

Auto insert closing greater than sign

I am trying to transition from cfeclipse. When I type a '<' I want cfbuilder to insert the closing '>' like it did in cfeclipse. If the tag I enter requires a closing tag then I type over the '>' with my own '>' and it closes the tag.
So, typing '<cfdump' gets me <cfdump>
typing '<cfoutput>' gets me '<cfoutput></cfoutput>'
and so on. Is there anyway to customize this behavior?

The closest you’ll likely get is under Preferences>ColdFusion>Profiles>Editor>Typing, where there is an option for “auto-close tags”. I don’t know that the choices offered will do exactly what you want, and I’m not aware of any way to customize such things, though it may well be possible.
also, in case you ask any follow-up questions, it could be helpful to indicate if you are talking about CFBuilder 3 or 2.
/charlie

Dreamweaver does not auto-complete /script tag

Dremaweaver CS5 Version 11.0 Build 4993 - does not close script tag. I type <script> include the text then type </ and the Script tag is NOT closed.
When I type </ the script tag should complete and close automatically.
So, for example:
<script type="text/javascript" language="javascript">
function closeThisWindow() {
window.close();
</
I have to type </script> because it does not auto-complete.
Thanks,
Don.

Good morning all,
Ok, Jon, thank you. I've not used a lot of </ within the scripts that I've written so, so far, that hasn't been a problem for me. Your explanation makes sense though. It also explains why it works if you select the option to: close after typing the opening tag's ">". Because once the opening and closing tags have been populated, entering </ would have no effect on the scripot tag at all.
Very nice response Jon. This behavior is crystal clear now and in fact, it seems to be a feature, not a bug.
Thank you,
Don.

Closing tag error

I have an extremely broken page.
When I validate it I get a lot of closing tag errors but I don't understand in what way I have not closed them properly as I have not had this issue before.
Can anyone help?
http://validator.w3.org/check?uri=http%3A%2F%2Fwww.tavcafe.com%2Fevents.php&charset=%28det ect+automatically%29&doctype=Inline&group=0

Thanks guys, that is all really helpful, unfortunately there is a problem.
I have just realised that when I validate the document it is including all of the code that is created through perch outside of the core document.
as you can see from bellow many of the errors are not present because they are created somehow by perch. I create the perch tags and templates and then I or my client enter in the information we required to be displayed within the perch admin panel and the code is automatically created, which is where those missing <ul> and <li> tags are occuring as well as the multiple nested span tags and the error on line 1139. As you can see I do have my css in a seperate document linked as you said and my
<doctype>
<html>
<head>
is in the format you suggest.
So how do I fix these code problems when it is autmated by Perch and there is no said document???
The document I am working on looks like this:
<?php include('perch/runtime.php');?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<head>
<title>TAV Cafe - Events</title>
<link rel="stylesheet" type="text/css" href="MyFontsWebfontsKit.css"/>
<link rel="stylesheet" href="colorbox.css" />
<link rel="stylesheet" href="gallery.css" />
<link rel="stylesheet" href="events.css" />
<style type="text/css">
@font-face {font-family: 'CallunaSans-Regular';
src: url('webfonts/23937E_0_0.eot');
src: url('webfonts/23937E_0_0.eot?#iefix')
format('embedded-opentype'),
url('webfonts/23937E_0_0.woff')
format('woff'),
url('webfonts/23937E_0_0.ttf')
format('truetype');
body {
    background-image:url(background_image.jpg);
    background-repeat:no-repeat;
    background-color:black;
    background-attachment: scroll;
    background-position:top left;
    background-size: 1024px 800px contain;
#hours { position:absolute;
left:10px; top:10px;
width:300px;
height:30px;
z-index:1;
font-family: Skia, CallunaSans-Regular;
font-size:13px;
font-weight:bold;
color:#a76d2f;
line-height:140%;
word-spacing:1px;
#title_bar { position:absolute;
left:0px; top:55px;
z-index:0;
.rollover a{
    display: block;
   text-indent: -9999px;
   margin: auto auto auto auto;
   cursor: pointer;
   outline: transparent solid 0px;
#title a{ position:absolute;
left:10px; top:70px;
height:86px;
width:325px;
z-index:1;
background: url('title.jpg') no-repeat left top;
#title a:hover{
   background-position: left 0px;
#about a{
position: absolute;
top: 55px; left: 440px;
height: 50px;
width: 128px;
background: url('about_tab.png') no-repeat left top;
#about a:hover{
   background-position: left -50px;
#gallery a{
position:absolute;
top: 55px; left: 655px;
height: 50px;
width: 168px;
background: url('gallery_tab.png') no-repeat left top;
#gallery a:hover{
   background-position: left -50px;
#venue a{ position:absolute;
left:910px; top:55px;
height: 50px;
width:215px;
background: url('venue_tab.png') no-repeat left top;
#venue a:hover{
   background-position: left -50px;
#shop a{
position:absolute;
left:550px; top:115px;
height: 50px;
width:128px;
background: url('shop_tab.png') no-repeat left top;
#shop a:hover{
   background-position: left -50px;
#restaurant a{
position:absolute;
top: 115px; left: 770px;
height: 50px;
width: 190px;
background: url('restaurant_tab.png') no-repeat left top;
#restaurant a:hover{
   background-position: left -50px;
#bar a{ position:absolute;
left:350px; top:115px;
height: 50px;
width:120px;
background: url('bar_tab.png') no-repeat left top;
#bar a:hover{
   background-position: left -50px;
#events a.events-link{ position:absolute;
left:50px; top:180px;
height: 50px;
width:140px;
background: url('events_tab.png') no-repeat left top;
#events a.events-link:hover{
   background-position: left -50px;
#events .events-calendar{ position:absolute;
left:50px; top:230px;
#pop_up_background { position:absolute;
left:340px; top:190px;
height:580px;
width:650px;
z-index:2;
div.scroll
background-color:transparent;
position:absolute;
left:380px; top:200px;
width:600px;
height:550px;
z-index:3;
font-family: Skia, CallunaSans-Regular;
font-size:16px;
color:#a76d2f;
line-height:140%;
word-spacing:1px;
overflow:scroll;
#contact_bar { position:absolute;
left:0px; top:635px;
z-index:1;
#contact a{
position:absolute;
top: 640px; left:0px;
height: 50px;
width: 190px;
z-index: 2;
background: url('contact_tab.png') no-repeat left top;
#contact a:hover{
   background-position: left -50px;
#copyright_background { position:absolute;
left:1020px; top:650px;
z-index:1;
#copyright { position:absolute;
left:1045px; top:755px;
font-family: Arial Black;
font-size:14px;
color:#340000;
line-height:110%;
z-index:2;
#webdesign { position:absolute;
left:1045px; top:660px;
font-family: PrestigeEliM-Reg;
font-size:18px;
color:#340000;
line-height:110%;
z-index:2;
.rollover a{
    display:block;
   text-indent:-9999px;
   margin: auto auto auto auto;
   cursor: pointer;
   outline: transparent solid 0px;
.rollover .events-calendar a{
   display:inline;
   text-indent:-9999px;
   margin: auto auto auto auto;
   cursor: pointer;
   outline: transparent solid 0px;
#website_link a{
position:absolute;
left:1020px; top:675px;
height: 76px;
width: 150px;
z-index:2;
background: url('website_link.png') no-repeat left top;
#website_link a:hover{
   background-position: left 0px;
#fb_icon a{ position:absolute;
left:280px; top:650px;
height: 36px;
width: 36px;
z-index:2;
background: url('fb_icon.jpg') no-repeat left top;
#fb_icon a:hover{
   background-position: left 0px;
#fb-root {position:absolute;
left:190px; top:655px;
z-index:2;
table.calendar {
    width:200px;
    height:200px;
    border-collapse: collapse;
    margin: 10px;
    clear: left;
    background-color:#eb5604;
table.calendar td {
    border: 1px solid #ccc;
    vertical-align: top;
table.calendar td.today {
    background-color:#483229;
    opacity:70%;
table.calendar td.today span.day {
    font-weight: bold;
    color: #bc5000;
table.calendar td.weekend {
    background-color: #483229;
table.calendar td.notinmonth {
    border: none;
    background-color: transparent;
table.calendar td.past {
    text-decoration: line-through;
table.calendar td.notinmonth.weekend {
    background-color: transparent;
table.calendar td span.day {
    display: block;
    color: #ccc;
table.calendar td div.event {
    display: block;
    background-color: #ffffff;
    color: #a76d2f;
    padding: 3px;
    border-radius: 5px;
    border: 1px solid #fff;
ul.calendar-nav {
    width: 200px;
    list-style: none;
    margin: 10px;
    padding: 0;
ul.calendar-nav li {
    width: 33.3%;
    list-style: none;
    margin: 0;
    padding: 0 0 10px 0;
    display: block;
    float: left;
    text-align: center;
ul.calendar-nav li:first-child {
    text-align: left;
ul.calendar-nav li:last-child {
    text-align: right;
/* --- LISTING --- */
ul.events {
    width: 200px;
    list-style: none;
    margin: 10px;
    padding: 0;
    border-top: 1px solid #bed6ec;
ul.events li {
    border-right: 1px solid #bed6ec;
    border-bottom: 1px solid #bed6ec;
    vertical-align: top;
    background-color: #bed6ec;
    clear: left;
ul.events li ul {
    list-style: none;
ul.events li li {
    border: none;
    border-bottom: 1px dotted #999;
    min-height: 0;
    margin-left: 25px;
    padding: 10px;
    background-color: #fff;
    clear: none;
ul.events li li:last-child {
    border-bottom: 0;
ul.events li li span.time {
    color: #999;
    font-style: italic;
    font-size: 90%;
    width: 60px;
    text-align: right;
    display: inline-block;
ul.events li li div.description {
    margin: 5px 0 0 63px;
    font-size: 86%;
    color: #555;
ul.events li li div.description p {
    margin: 0 0 1em 0;
ul.events li span.day {
    font-weight: bold;
    font-size: 250%;
    float: left;
    color: #0a86d2;
    text-align: right;
    width: 50px;
    margin: 0 0 0 1px;
    padding: 0 15px 0 0;
    line-height: 1;
    border-top: 1px solid #fff;
ul.events li:first-child span.day {
    border-top-color: #bed6ec;
ul.event-listing-nav {
    width: 200px;
    list-style: none;
    margin: 10px;
    padding: 0;
    clear: both;
ul.event-listing-nav li {
    width: 33.3%;
    list-style: none;
    margin: 0;
    padding: 0 0 10px 0;
    display: block;
    float: left;
    text-align: center;
ul.event-listing-nav li:first-child {
    text-align: left;
ul.event-listing-nav li:last-child {
    text-align: right;
ul.event-listing-nav:after {
content: ".";
display: block;
height: 0;
clear: both;
visibility: hidden;
ul.custom-listing {
    margin: 0;
    padding: 0;
    list-style: none;
    width: 200px;
ul.custom-listing li {
    padding: 0 0 1em 0;
    margin: 0 0 1em 0;
    border-bottom: 1px solid #ccc;
table.calendar td div.event {
    position: absolute;
    display: none; /* keeps the popup hidden if no JS available */
table.calendar td {
    position: relative;
</style>
<script src="http://code.jquery.com/jquery-1.8.2.min.js" type="text/javascript"></script>
    $(function () {
        $('table.calendar td').each(function () {
            // options
            var distance = 10;
            var time = 150;
            var hideDelay = 100;
            var hideDelayTimer = null;
            // tracker
            var beingShown = false;
            var shown = false;
            var trigger = $(this);
            var popup = $('div.event', this).css('opacity', 0);
            // set the mouseover and mouseout on both element
            $([trigger.get(0), popup.get(0)]).mouseover(function () {
                // stops the hide event if we move from the trigger to the popup element
                if (hideDelayTimer) clearTimeout(hideDelayTimer);
                // don't trigger the animation again if we're being shown, or already visible
                if (beingShown || shown) {
                    return;
                } else {
                    beingShown = true;
                    // reset position of popup box
                    popup.css({
                        'z-index': 1000,
                        top: 30,
                        left: 10,
                        display: 'block' // brings the popup back in to view
                        // (we're using chaining on the popup) now animate it's opacity and position
                            .animate({
                                top: '-=' + distance + 'px',
                                opacity: 1
                            }, time, 'swing', function() {
                                // once the animation is complete, set the tracker variables
                                beingShown = false;
                                shown = true;
            }).mouseout(function () {
                        // reset the timer if we get fired again - avoids double animations
                        if (hideDelayTimer) clearTimeout(hideDelayTimer);
                        // store the timer so that it can be cleared in the mouseover if required
                        hideDelayTimer = setTimeout(function () {
                            hideDelayTimer = null;
                            popup.animate({
                                top: '-=' + distance + 'px',
                                opacity: 0
                            }, time, 'swing', function () {
                                // once the animate is complete, set the tracker variables
                                shown = false;
                                // hide the popup entirely after the effect (opacity alone doesn't do the job)
                                popup.css('display', 'none');
                        }, hideDelay);
var _gaq = _gaq || [];
_gaq.push(['_setAccount', 'UA-35744229-1']);
_gaq.push(['_trackPageview']);
(function() {
    var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
    ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
    var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
</script>
</head>
<body>
<div id="fb-root"></div>
<script>(function(d, s, id) { type="text/javascript"
var js, fjs = d.getElementsByTagName(s)[0];
if (d.getElementById(id)) return;
js = d.createElement(s); js.id = id;
js.src = "//connect.facebook.net/en_US/all.js#xfbml=1";
fjs.parentNode.insertBefore(js, fjs);
}(document, 'script', 'facebook-jssdk'));</script>
<div id="hours">
<strong>Open:<br />Tuesday-Sunday (二～日)<br /> 11:30am - 2:00am (3:00am 五 & 六)</strong>
</div>
<div id="title_bar">
<img src="title_bar.jpg" alt=""/>
</div>
<div class='rollover' id="title">
<a href="index.php">
</a>
</div>
<div class='rollover' id='about'>
<a href="about.php">
</a>
</div>
<div class='rollover' id='gallery'>
<a href="gallery.php">
</a>
</div>
<div class='rollover' id='venue'>
<a href="venue.php">
</a>
</div>
<div class='rollover' id='shop'>
<a href="shop.php">
</a>
</div>
<div class='rollover' id='restaurant'>
<a href="restaurant.php">
</a>
</div>
<div class='rollover' id='bar'>
<a href="bar.php">
</a>
</div>
<div id="pop_up_background">
<img src="pop_up_2.png" alt=""/>
</div>
<div class="scroll">
<?php
$opts = array(
'filter'=>'eventDateTime',
'match'=>'eqbetween',
'category'=>array('gigs', 'Events'),
'sort'=>eventDateTime,
'sort-order'=> ASC,
'display'=>date,
'value'=>$_GET['id'],
'template'=>'events/listing/event-day.html',
perch_events_custom($opts);
?>
</div>
<div id="contact_bar">
<img src="contact_bar.png" alt=""/>
</div>
<div class='rollover' id='events'>
<a class='events-link' href="events.php">
</a>
    <div class='events-calendar'>
        <?php
             * setting options for the calendar. Change the categories listed to one or more which exist in your admin.
            $opts = array(
                'template'=>'calendar.html',
                'past-events'=>true,
                'category'=>array('gigs', 'Events')
            perch_events_calendar($opts);
        ?>
    </div>
</div>
<div class='rollover' id='contact'>
<a href="contact.php">
</a>
</div>
<div id="copyright_background">
<img src="copyright_bgrd.png" alt=""/>
</div>
<div id= "webdesign">
Webdesign
</div>
<div id= "copyright">
© TAV Cafe
</div>
<div class='rollover' id='website_link'>
<a href="http://www.renflannery.com/" target="_blank">Visit W3Schools</a>
</div>
<div class='rollover' id='fb_icon'>
<a href="https://www.facebook.com/TAVCafe" target="_blank">Visit W3Schools</a>
</div>
<div class="fb-like" id="fb-root" data-href="http://www.tavcafe.com" data-send="false" data-layout="button_count" data-width="450" data-show-faces="false" data-font="verdana"></div>
</body>
</html>

How to do closing tag: tag /tag instead of tag/ in jdev xslt mapper

Hi!
We have commercial systems, which cannot work with short closing tags for empty nodes.
Xslt mapper for oracle mediator optimize everytime to short closing tag, when node content is empty.
Is there a property or technique to achieve long closing tags?
Kind regards
Torsten

http://www.biglist.com/lists/xsl-list/archives/200610/msg00342.html
not really a pretty solution, but you could try adding the comments

Avoid explicit closing tag in XML using graphical mapping

Hi,
I created a data type with an element called TAG1 which has an attribute called attr.
I mapped an empty constant to the element and the value XXX to the attribute. I`m using graphical mapping and the XML I get is the following:
<TAG1 attr = u201CXXXu201D></TAG1>
But for reasons of volume I need to generate the XML without the explicit closing tag, such as:
<TAG1 value = u201CXXXu201D/>
Is there any possibility to achieve this with graphical mapping?
Thanks & Best Regards,
Viviana

> But for reasons of volume I need to generate the XML without the explicit closing tag, such as:
>
> <TAG1 value = u201CXXXu201D/>
>
> Is there any possibility to achieve this with graphical mapping?
This is not posible. The graphical mapping always creates start and end tag, even for empty elements.
You need a seperate mapping step with XSLT or Java mapping.
Regards
Stefan

Auto highlight correction in LR 4

Is Adobe even considering adding the option of turning off the auto highlight correction inserted into LR4. For anyone shooting white backgrounds this is a terrible nuisance. I personally will have to switch to another image processing software program if there is not a fix for this. I work hard to get a good image in camera with a pure white background, then Lightroom messes with it automatically. It seems someone at Adobe would have realized it was not a good idea to assume that no photographers would want a pure white background.

I tried to get Krista to send me the raw, but she/he has moved on - given up on PV2012 due to difficulty preserving fine detail in upper highlights whilst maintaining solid white background.
It is true that there are 2 potentially bad things about PV2012:
1. It doesn't like for you to have all white or all black anything (auto highlight recovery and auto shadow recovery). - this is usually, but not always, a great thing...
2. PV2012 can lose fine detail in the whites due to compression done presumably to preserve tone & color relationships when 1 or more channels are clipped., but yielding a less-than-optimal trade off in some cases, see this thread:
http://forums.adobe.com/thread/1050188?tstart=0
Don't get me wrong. It could be that these photos would look stellar with a little more finessing of whites/exposure/highlights to bring out detail in the brighter highlights (and maybe some clarity). But also, its possible that Krista has indeed bumped up against one of PV2012's not-so-good "features", and he/she knows it, and isn't willing to "fight" with it to get satisfactory results.
Summary: In general, PV2012 handling of upper highlights / whites / clipping is very nicely done, but in some photos, it's "potential" bad things become real bad things.
Krista - have you tried negative highlights? It may be that you need to go easier on the +whites, and/or enhance highlight detail using -highlights, then paint the surrounding wall white if need be. Hard to tell without having a raw to work with. Also, your exposure may need to be dropped, especially if you've bumped the whites.
In general, in PV2012, I think it's best to handle subject detail and white wall separately - i.e. do what you need to do to get the subject looking nice, then use locals to repaint the wall, if you really want it solid white. If you don't want to resort to locals for repainting the background, then you won't be the first to abandon PV2012 for "product photos" against white (or black) backgrounds. And also or instead of, consider using locals to further enhance subject. I sometimes crank whites up a little much then use -highlights locally in selected areas.
PS - I hope there is a PV2014 which further improves Lightroom's ability to deal optimally with upper highlights / whites, for all cases... (ditto for blacks).
I adore PV2012 in most (but not all) ways.
UPDATE: I couldn't resist downloading the posted jpeg samples in lieu of a raw to work with. I think it's entirely possible that Krista is losing detail in the wings due to the "White Mud" phenomenon - PV2012, in it's quest for recovering blown background and integrating with the rest of the photo, may be compressing the non-blown whites (brightest part of insect's wings). I think this phenomenon has become my least favorite aspect of PV2012. It affects not only photos with white backgrounds, but any photo with blown highlights - and it doesn't necessarily take a lot of blown pixels to negatively influence all whites in the photo (even if all such pixels have been cropped out!). Reminder: +whites is far from a panacea in dealing with "white mud syndrome". A tone curve with an upward inflection in the whites can help a little, but only a little - push it too far and the rest of the image will deteriorate.
I don't think Adobe has any intention of improving this in PV2012 - hope I'm wrong. They could add another control in a fashion that doesn't influence previous edits, to refine handling of top-most whites, and release it as a minor revision - I would be both shocked and delighted if they did that.
UPDATE #2: After further consideration of the jpeg (really wish I had that raw), I have reversed my previous hypothesis. I thiink this is a photo that can be processed to perfection, easily, in PV2012, even with almost completely clipped background. Note: the following enhancements were made to the (already processsed and baked) PV2012 jpeg, and so may NOT apply to the raw.
* Much Lower Exposure (high exposure was compressing upper highlights)
* Much Lower Contrast - this is a photo where (presumably) high contrast is not desirable, and the upper half of the tonal range is nicely served simply by dropping contrast.
* Negative Highlights - a lot: wing detail is totally recoverable / enhanceable (NOT a victim of "White Mud Syndrome").
* Positive Shadows - same amount as Negative Highlights (except positive, not negative).
* Positive Whites - just enough to clip the background, no more.
* Positive Blacks - a lot: in this case, it helps maintain the "softer" look of the PV2010 version, and keeps intra-shadow contrast down. - brightens the photo with less highlight compression than exposure.
* No Clarity - totally unnecessary, and gives it a harsher look.
* No Tone Curve - totally unnecessary.
Example for comparison (hint: context-click and open in new tab, then in WebPhotoBrowser: click next, next, next to compare, instead of next, prev, next, prev...)
Krista - Consider practicing more with PV2012. It is far more capable than it seems at first. I mean, continue to use PV2010 if need be, or you're in a hurry... - but keep honing your PV2012 skills too!
PV2012 rocks!
Cheers,
Rob

How to make an explicit closing tag in XML(e4x).

I'm working with some XML data and I'm having trouble forcing the way my closing tags are generated.
I want the long hand form, such as:
var xmlData:XML =
<code>
<codeSnippet>
</codeSnppet>
</code>;
But when I try to insert nodes within the codeSnippet node as child nodes(<snippet />, etc.), and then write to a file, it
makes the codeSnippet node look like <codeSnippet /> and the <snippet /> nodes are after, which will not work.
How can I make it NOT treat an empty node as <codeSnippet /> and explicitly keep it as in long hand form, such as:
<codeSnippet>
</codeSnppet>
Thanks...
fd

I figured it out for myself.
So, does that mean I get the 10 points?
fd

Closing tag in xml transformation

Hi experts,
I have the following ABAP code:
ABAP itab to XML string
CALL TRANSFORMATION id SOURCE data = ti_stocks[]
                         RESULT XML    ps_output.
The result in ps_output should be an xml like this
<?xml version="1.0" encoding="utf-16" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<DATA>
<ZTABLE_STO>
<FIELD1 /> ABC</FIELD1>
<FIELD2 />0300</FIELD2>
<FIELD3 />1</FIELD3>
</ZTABLE_STO>
etc.
However, if my internal table ti_stocks contains the field1 with an empty value then the xml is incorrect without its corresponding closing tag:
<?xml version="1.0" encoding="utf-16" ?>
<asx:abap xmlns:asx="http://www.sap.com/abapxml" version="1.0">
<asx:values>
<DATA>
<ZTABLE_STO>
<FIELD1 />
<FIELD2 />0300</FIELD2>
<FIELD3 />1</FIELD3>
</ZTABLE_STO>
etc.
How can I resolve this problem? I would like to have an open tag and a closing tag for every field.
FIELD1 is a char type field.
Thank you,
Oscar
Edited by: Oscar Arranz on Jan 26, 2012 2:46 PM

Hello everyone, sorry for my english, I had the same requeriment for the end tag, the simple transformation give this result <xxx/> when the value was empty, and I did something similar to Oscar,
i did the simple transformation and the result whas and xstring, i used a function to pass it to string, and then I make a replacement.
here is some code:
* Genera XML
   data: xml_xstring          type xstring.
   data: w_xml                 type string.
   data: ixml                    type ref to if_ixml,
           streamfactory      type ref to if_ixml_stream_factory,
           encoding             type ref to if_ixml_encoding,
           ixml_ostream      type ref to if_ixml_ostream.
   data: resstream           type ref to if_ixml_ostream.
****Create an instance of the Ixml Processor
   ixml = cl_ixml=>create( ).
* ****Create the Stream Factory
   streamfactory = ixml->create_stream_factory( ).
* ****Create an Endcoding and Byte Order
   encoding = ixml->create_encoding( character_set = 'ISO-8859-1' byte_order = 0 ).
* * ****Create the output stream with a pointer to our binary string
   ixml_ostream = streamfactory->create_ostream_xstring( xml_xstring ).
* ****Set the Encoding into a stream
   ixml_ostream->set_encoding( encoding = encoding ).
****Call simple Transformation
   call transformation zdte_libros
   source zcaratula = x_doc
   result xml ixml_ostream.
*From xstring to string.
   call function 'HR_RU_CONVERT_HEX_TO_STRING'
          exporting
                 xstring = xml_xstring
          importing
                 cstring = w_xml.
* <xxx/> to <xxx><xxx/>
   replace all occurrences of regex '<([^><\s]+)( [^><]+)?/>' in w_xml with '<$1$2></$1>'.
Hope it helps someone with the same problem .

Auto collapse SVG tags (or other tags) to clean up HTML structure

I am usong SVG for icons and logos in the my HTML. I know Dreamweaver CC allow collapsing of code sections highlited, but I would like to be able to set a setting to auto collapse certain tags to help make the HTML more readable. Is there and option/script/extension to do this?
I dislike how "Apply Source Formatting" will expand collapsed sections, requiring you to go re-collapse them manually.

As far as I've ever seen, there's nowhere in DW where you could set something like that. Aside from hitting Ctrl + Shift + J while anywhere within the tag to collapse it, I think you're stuck.
It would be a nice addition to the Tag Library Editor.
Here is the official bug report/feature request form: https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform

ACE-4710 : XML Syntax Error du to a missing closing tag

Hi,
We use XML over HTTPS to gather connections information from a management station. We can successfully read the number of connections per real server (rserver), but the ACE returns a buggy XML code when we tray to get the number of connections through the VIP (by asking the service-policy). The problem is a missing closing tag in the returned code. The missing tag is </sp_class_map>.
We have the latest ACE software version A3(2.2) installed. Note that the same request on a ACE Service Module does not presents this bug. I took a look in the bug toolkit but did not found the exact match.
Does somebody already had this problem ? it is anoying as we cannot represent the number of connections for a specific vip in the NMS.
I attach the returned XML code, in which I highligted the tad that does not have its closing counterpart.
Thank you for any info before I open a TAC case
Yves

Thank you Gilles,
It seams that this bug is only visible inernally : "Information contained within bug ID CSCsz52234 is only available to Cisco employees".
I saved the bug to be informed on its status. Do you thing I should open a TAC case anyway ?
Yves

Setting node value of self closed tags

Hi all, I was just wondering if anyone knew the answer to this problem, I'm new to this level of java programming and I've been reading documentation till my eyes have started bleeding. When I use the setNodeValue() function on an element, it works fine UNLESS the node is self closed, in which case i cannot access it as it comes up as null. If anyone can give a sample code, or point me in the right direction I'd appreciate it

by "it" i mean the node itself, and by "comes up as", i mean that the value of the node (and data type apparently) is null. Here is the code snippet that i currently have;
NodeList nodeLst = doc.getElementsByTagName(repeatedNode);
for (int s = 0; s < nodeLst.getLength(); s++) {
     Node fstNode = nodeLst.item(s);
     if (fstNode.getNodeType() == Node.ELEMENT_NODE) {
          Element fstElmnt = (Element) fstNode;
          NodeList fstNmElmntLst = fstElmnt.getElementsByTagName("status");
          Element fstNmElmnt = (Element) fstNmElmntLst.item(0);
          Node test = (Node) fstNmElmntLst.item(0);
          if (fstNmElmnt != null){
               NodeList fstNm = fstNmElmnt.getChildNodes();
               if ( ((Node) fstNm.item(0)) != null ){
                    ((Node) fstNm.item(0)).setNodeValue("testing setvalue");
}Notice the checks against null that I have in the code, those are to check against the self closed tages (eg <node />). I realize that there is nothing wrong with xmnl being formatted in this way, I just need to find a way to set values in those nodes. From reading the documentation on setNodeValue() ( [http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/Node.html#setNodeValue(java.lang.String)|http://java.sun.com/j2se/1.4.2/docs/api/org/w3c/dom/Node.html#setNodeValue(java.lang.String)] ), the function cannot be used on a node that is of type null. What I'm trying to figure out is what to use instead yo be able to set the values of those "null" nodes.
Edited by: Billy1234 on Jul 3, 2008 6:01 AM

Auto Highlight Closing Tags

Similar Messages

Maybe you are looking for