<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">It doesn't have semantic value but I also don't see the harm. As easy as we try to make the process of switching themes to be, in a real situation it rarely is. I know the frustration when your content styling is gone but I also know the one when your theme is orange and your shortcodes are blue. Also, post thumbnails are a theme-supported feature, yet when you switch a themes you always find them out of shape and need to regenerate them. There's no such thing as content that fits anywhere. We need to either set a standard or become more relaxed.<div><br></div><div>Daniel</div><div> <br><div><div>On Mar 3, 2013, at 4:23 PM, Chip Bennett wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Let's back up a bit: why would <span class="foo bar"></span> be added to post content to begin with? What is the semantic meaning of such a container?</div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Sun, Mar 3, 2013 at 9:16 AM, Daniel Tara <span dir="ltr"><<a href="mailto:contact@onedesigns.com" target="_blank">contact@onedesigns.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word">Speaking a bit more generally I believe there always be this conflict between content generation and content presentation. Content generation is plugin territory but if plugins also add their own styling what are the chances that styling fits a random theme. I say not styled content is better than ugly styled content. I think we should allow more middle ground here.<span class="HOEnZb"><font color="#888888"><div>
<br></div><div>Daniel</div></font></span><div><div class="h5"><div> <br><div><div>On Mar 3, 2013, at 4:10 PM, Ünsal Korkmaz wrote:</div><br><blockquote type="cite">Thank you for review but i mean tinymce does not adding shortcode, it adds css code.<div>
<a href="http://themes.svn.wordpress.org/firmasite/1.1.0/functions/shortcodes.php" target="_blank">http://themes.svn.wordpress.org/firmasite/1.1.0/functions/shortcodes.php</a></div>
<div>Those shortcodes are wordpress's default shortcodes. audio, gallery, video.<br><br><div class="gmail_quote">On Sun, Mar 3, 2013 at 4:07 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net" target="_blank">chip@chipbennett.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hmm, actually, there *are* shortcodes:<div><a href="http://themes.svn.wordpress.org/firmasite/1.1.0/functions/shortcodes.php" target="_blank">http://themes.svn.wordpress.org/firmasite/1.1.0/functions/shortcodes.php</a><br>
</div>
<div><br></div><div>And this is definitely Plugin territory:</div><div><a href="http://themes.svn.wordpress.org/firmasite/1.1.0/functions/remove-comments-absolute.php" target="_blank">http://themes.svn.wordpress.org/firmasite/1.1.0/functions/remove-comments-absolute.php</a><br>
</div><div><br></div><div>And a good deal of this is Plugin territory:</div><div><a href="http://themes.svn.wordpress.org/firmasite/1.1.0/functions/fix.php" target="_blank">http://themes.svn.wordpress.org/firmasite/1.1.0/functions/fix.php</a><br>
</div><div><br></div><div>And this is also probably Plugin territory (though a bit of a gray area):</div><div><a href="http://themes.svn.wordpress.org/firmasite/1.1.0/functions/custom-sharing-buttons.php" target="_blank">http://themes.svn.wordpress.org/firmasite/1.1.0/functions/custom-sharing-buttons.php</a><br>
</div><div><a href="http://themes.svn.wordpress.org/firmasite/1.1.0/functions/custom-facebook-comments.php" target="_blank">http://themes.svn.wordpress.org/firmasite/1.1.0/functions/custom-facebook-comments.php</a><br></div>
<div><br>
</div><div>But, for the TinyMCE buttons: my initial reaction would be to say that they also are probably Plugin territory. What do the buttons do? What do they add to the post content? Wrap selected content in <span class="foo bar"></span> tags? Sure, that degrades more gracefully than un-parsed shortcodes, but it would still result in a bunch of unused markup scattered throughout the user's posts after switching Themes. <b>Thus, I would say that the TinyMCE buttons are also Plugin territory</b>. I would recommend defining the *styles* for the CSS classes added via the TinyMCE buttons, but make the underlying TinyMCE button functionality itself a Plugin.</div>
<div><br></div><div>Regards,</div><div><br></div><div>Chip</div></div><div class="gmail_extra"><br><br><div class="gmail_quote"><div><div>On Sun, Mar 3, 2013 at 8:00 AM, Ünsal Korkmaz <span dir="ltr"><<a href="mailto:unsalkorkmaz@gmail.com" target="_blank">unsalkorkmaz@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>Hi,<div>My theme:</div><div><a href="http://themes.trac.wordpress.org/ticket/11437" target="_blank">http://themes.trac.wordpress.org/ticket/11437</a></div>
<div>Theme is adding custom tinymce button that adds css code for design elements. There is no shortcode or something.. just css code. </div>
<div>Its allowed in themes right?</div>
<br></div></div><div>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></div></blockquote></div><br></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br><a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote></div><br></div></div></div></div><br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br></div>
_______________________________________________<br>theme-reviewers mailing list<br><a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>http://lists.wordpress.org/mailman/listinfo/theme-reviewers<br></blockquote></div><br></div></body></html>