MULTILINGUAL Custom fields and pic descriptions MULTILINGUAL Custom fields and pic descriptions
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

MULTILINGUAL Custom fields and pic descriptions

Started by johnvamo, March 17, 2005, 10:54:40 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

johnvamo

Hello,

I think it could be very useful to be able to have multi-lingual features for custom fields and if possible for description fields too...If you have language options why not this add-on? ???

Thanks, and congratulations for the great job with coppermine. ;D

Tranz

What kind of "multi-lingual features" are you referring to?

ypp

#2
I think could be interesting so:

I'd like to choose different languages to describe the same picture and every one of these translated descriptions should appears in its appropriated language section (not all together). It should be with a default language for all the language sections I've not used.


...the same could be for categories and albums ::)

Oscommerce script uses a simile system...

bye

Joachim Müller

has been requested and discussed before. Would be a bloat feature imo. Turned down.

larshaervig

Quote from: GauGau on November 14, 2005, 08:02:00 AM
has been requested and discussed before. Would be a bloat feature imo. Turned down.

Why exatly ? Because it is a huge effort to make or ?. I thisk it is a natural request. Langiage support har , almost, no meaning without support for language in eg. picture text ot comment etc.

regards
Lars
___________________________________________________________________
Gallery : foto.laptus.dk

Joachim Müller

- because only a very small number of coppermine users would actually use it.
- because it would mean a huge performance penalty
- because it would mean a lot of work to build this functionality