How To translate element properties?

31 Posts

wildcat Reply #1, 16 years, 2 months ago

Hi,
I have made a french translation of the snippet properties, using a lexicon file (properties.inc.php) in the dewplayer package; however it seems not to work, i.e. descriptions of the properties still remain in english (not that it’s bad laugh

but would be great to translate that wink

).
Am I missing something?
The properties of the snippet do have dewplayer:properties in the lexicon field so that it’s linked to the lexicon file, but doesn’t seem to work... Any advice? I didn’t find any documentation on how to translate element properties,

Thanks for your help,
Kevin

24,544 Posts

BobRay Reply #2, 16 years, 2 months ago

Have you tried reinstalling the snippet? The descriptions may be set during installation.

Otherwise, you could try going to System -> Lexicon Management and looking at the dewplayer namespace and the properties topic to see if you can change them there (or import your topic file).

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

31 Posts

wildcat Reply #3, 16 years, 2 months ago

Hi Bob,
I’m the author of the dewplayer package, it has been packaged with PackMan and it’s including the folder of the lexicon entries.
I have checked in system ->lexicon management, the dewplayer namespace is here but not the properties topic... So maybe a PackMan issue?

24,544 Posts

BobRay Reply #4, 16 years, 2 months ago

Quote from: wildcat at Aug 19, 2010, 03:18 AM

Hi Bob,
I’m the author of the dewplayer package, it has been packaged with PackMan and it’s including the folder of the lexicon entries.
I have checked in system ->lexicon management, the dewplayer namespace is here but not the properties topic... So maybe a PackMan issue?

That’s a good guess. PackMan is for fairly simple packages. You may have to create a traditional transport package script.

You could report the problem here: http://github.com/splittingred/PackMan/issues

It just occurred to me that if you put all the lexicon strings in the "default" topic, you’d probably have them.

Another question is whether you have the properties strings in the right place. I believe they would go in:

core/components/dewplayer/lexicon/fr/properties.inc.php

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

31 Posts

wildcat Reply #5, 16 years, 2 months ago

correct, this is were the files are located. I’m going to file an issue into PackMan, as a feature request. I had a look at the Quip component, and it seems that properties lexicon entries should be named as ’packagename.prop_propertyname’, that wasn’t the case... will have to copy the transport package build script also wink

(would be great if we could have a ’generic’ build script that follows the general package structure of splittingred packages, i.e. CMP, snippets, chuncks, lexicon entries, etc...)
Thanks Bob,

24,544 Posts

BobRay Reply #6, 16 years, 2 months ago

There is a generic build script in the SVN add-on component repository called "component template" iirc, but I think it’s fairly out-of-date with respect to some of the constants and how the lexicon is handled.

Maybe there’s something newer at GitHub -- I haven’t had time to look.

Did I help you? Buy me a beer
Get my Book: MODX:The Official Guide
MODX info for everyone: http://bobsguides.com/modx.html
My MODX Extras
Bob's Guides is now hosted at A2 MODX Hosting

4,149 Posts

splittingred Reply #7, 16 years, 2 months ago

I’ve been meaning to put Doodles up there. I’ll try and take a look at that tomorrow.

shaun mccormick | bigcommerce mgr of software engineering, former modx co-architect | github | splittingred.com

31 Posts

wildcat Reply #8, 16 years, 2 months ago

Thanks Shaun

(http://github.com/splittingred/modExtra)

31 Posts

wildcat Reply #9, 16 years, 2 months ago

Sorry but I have a few more questions on the ’properties.modExtra.php’ file; I tried to export the property set from modx but this gives me a js file and I’m not sure if the php file will have the same layout/values,

What are the possible values for the type? textfield, list, ,numberfield combo-boolean
What is the syntax for options? is this an array, or a kind of csv entries with the couple name:value?

Thanks,

Edit: solved:

array(
        'name' => 'sortBy',
        'desc' => 'prop_feo.sortby_desc',
        'type' => 'list',
        'options' => array(
            array('text' => 'feo.filename','value' => 'filename'),
            array('text' => 'feo.date','value' => 'date'),
            array('text' => 'feo.size','value' => 'size'),
            array('text' => 'feo.extension','value' => 'extension'),
        ),
        'value' => 'filename',
        'lexicon' => 'filelister:properties',
    )