[TYPO3-core] RFC #11177: Feature: New options noRescale and resolutionFactor for getImgResource()

[Ries van Twisk]

On May 25, 2009, at 2:35 AM, Franz Koch wrote:

> Hi Stefan,
>
>>> sorry, I like the general idea, but I don't like the way it's done.
>>> The "resolutionFactor" is somewhat odd to me. For me it would make
>>> much more sense to actually define the dpi (Dots Per Inch), so that
>>> based on the given width and height and the dpi you can calculate  
>>> the
>>> total dimensions (default for screen are 72dpi).
>>
>> OK: I will change that.
>> Is the screen-resoution always 72dpi (in this case) or should I use  
>> the
>> settings in localconf $TYPO3_CONF_VARS['GFX']['TTFdpi'] ?
>
> screen resolution is afaik always 72dpi - and even if not it would
> depend on the output device that you can't control. All images for the
> web are generated with 72dpi.
>
> But before changing things based on my personal taste I'd wait for
> others to give feedback.


DPI For screen doesn't make sense, DPI is used for raster images only  
(print industry)

See it like this: if your screen is 42" with a resolution of 1024x768  
then your so called 'DPI'
is totally different then a 10" netbook with the same resolution.  
(both are not 72 DPI).

So a DPI setting for screen media is totally bogus.

also, that the setting the in the install tool 'works' doesn't mean  
the setting is right,
it has properly something to do with internal processing of text on  
images.

So please stay away from any DPI setting in typo3 for images and text  
(except for that TTFDPI thing??)

just my 2 cents

PS: Shouldn't this be discussed on typo3-dev???

Ries