Disable translations per type of content

Similar to fields, where we have the power to say that the IMAGE FIELD is untraslatable, I wounder if we could have this same feature but PER CONTENT TYPE, I explain, I have this type of contetent called SLIDESHOW IMAGES or CITYES. An I don't for my team or the client WASTE time translating this items, becouse they are really not traslatable. Wouldbe nice to define this on a per type of content bases.

Thanks.

Hello,

what does an untranslatable content type involve ?

what behavior?
have you thought of what will be disallowed ?

e.g. an untranslatable content type will involve:
-- allowed language to be only "ALL" in NEW item form that have content
-- when a content is submitted that content type is being preloaded (we have menu items that the user sees a number of allowed (via ACL) content types and selects content type),
then after item is submitted the language must be changed to ALL and user must be notified ...
-- the associations of translations must be disallowed
-- maybe more


So some requests are not trivial ... to implement and involves dealing with unexpected or unwanted behavior that we will force as to do more work

e.g. the untranslatable feature for fields was fixed several times in a couple of different places, and involved more work than we initially had in mind ...

Din't know that it was that complexo , thought it was a trivial change.

I can live with this

3.x is more important rigth now.

Hello,

yes 3.x support should be finished before any other feature,

PS:
some new filter improvements (including the custom field scope = like locked filter values of category view)
and some other improvements were done now , because of paid work