[PATCH] Add long comments to shared-mime-info XML file

Brian J. Tarricone bjt23 at cornell.edu
Thu Oct 13 13:26:42 PDT 2005

On 10/13/2005 3:17 AM, Christian Neumair wrote:
> Am Mittwoch, den 07.09.2005, 23:48 -0400 schrieb Andrew J. Montalenti:
>>I don't know about this patch.  Some of your long forms are a bit too
>>long.  "Cascading Style Sheets stylesheet" and "Microsoft Windows Media
>>Video video", for example, are particularly long and redundant, and
>>would look stupid should a programmer ever actually employ the long
>>comment form.
> Maybe you could come up with alternate proposals?

Easy.  Actually *read* each long comment to see if they make sense and
don't have redundant text, and fix the ones that are problematic.  This
sounds like a case of expanding "LCD display" into "Liquid Crystal
Display display" and thinking that's not redundant.  For things like
"WMV video" -> "Windows Media Video", drop the extra term.  For things
like "CSV spreadsheet" -> "Comma-Separated Values spreadsheet" (just
making up a contrived example), leave it as-is.

>>Since a lot of what you are doing seems to be acronym expansion, I think
>>a better approach might be to use what many web pages employ nowadays,
>>namely an <abbr> tag.

Behdad Esfahbod wrote:

> What about going the exact HTML way:
>   <_comment><abbr title="Cascading Style Sheets">CSS</abbr> stylesheet</_comment>
> Assuming that the long-comment is typically useless, this way you
> have the short comment "CSS stylesheet" that most people want,
> and you can have a tooltip for the under-dotted-lined "CSS", like
> the browsers do these day.

Please don't.  Now compliant implementations need to know how to parse a
tiny useless subset of HTML?  Seems silly to me.  I'm fine with
<comment> and <long-comment>, but please, whatever is decided, don't try
to overcomplicate it: just use two separate tags, whatever they're named.


More information about the xdg mailing list