Why is "input format" not called "output format" or "display format"? After all the content of the node is unfiltered raw data and the filters which form the "input format" are only applied when the raw data is displayed.

Puzzled newbie.

Comments

vm’s picture

sort of frivilous but I'll bite:

I can make the argument that the input format is correct because it is what is put into a node. I've never even heard the term "output format" before reading this thread.

_____________________________________________________________________
Confusious says:
"Those who seek drupal answers should use drupal search!" : )

rockoyster’s picture

This is not the slightest bit frivolous and I have done a search with no success. I am seriously intrigued by the terminology. Maybe the way it is, is a Belgian thing?

If I create content in Greek and nominate an "input format" which includes a Greek to English filter then my page will display in English. ie it is a filter which affects the display NOT the input. The page is still stored in Greek in node-revisions but is displayed in English or if I have a Greek to Mandarin filter it will be displayed in Mandarin. How the hell can it be call an "input format"?

BTW its "Confucius".

cog.rusty’s picture

Interesting idea for a filter. But being a Greek, I won't hold my breath.

Here is a reasoning for the terminology (not a Belgian one):

The existing Input Formats, "Filtered HTML", "Full HTML" and "PHP code" are all expected to produce the same kind of themed output. What the user is looking for is what kinds of input are allowed for achieving this output. Hence "Input Formats".

The Input Formats contain a series of filters. These filters apply on the user input to produce the output. They do that late, at the time when output is produced, however, they are still applied to the (stored) input.

So, filters (not Input Formats) could be called input filters or output filters, depending on the aspect where you want to place the emphasis and to what you need to contrast them to make it more intuitive for the user to find them.

Your point about Input Formats becomes more "to the point" when some conversion filters totally transform the content, in which case Input Formats would not be the most intuitive place for the user to look for them. An "Autotranslator" filter would stretch the concept of an Input Format, agreed.

vm’s picture

Thanks for responding to my signature, Though it wasn't intended for you or your question, it's nice to know that it does indeed get read : ). Just happens to be at the bottom of all my posts. ; )

Also Thanks! for the Confucius correction!

_____________________________________________________________________
Confucious says:
"Those who seek drupal answers should use drupal search!" : )

cog.rusty’s picture

Actually I was thinking the "s" was a pun for a Confusion effect. Besides, if someone says "Confucius didn't say that" you can answer "Sure, Confusious did".

Confusious gets 29,800 google hits
Confusius gets 75,700 hits

And the less inspired ones:

Confucious gets 252,000 hits
Confucius gets 4,680,000 hits

vm’s picture

If only I could rotate the text there, I'd use all 4 versions : )

_____________________________________________________________________
Confucius says:
"Those who seek drupal answers should use drupal search!" : )

cog.rusty’s picture

Probably because it doesn't format anything. It just accepts and transforms some "formats" of input.