WDX Content Plugin: ImgSize

[J.Bl]

Hello,

2J.Bl
- Please, write TOTAL_COMMANDER "as is" in the subject, in order I can recognize you mail for a first contact (to avoid the dust-bin).

Done.


ImgSize updated to Version 1.04. New in this version: IniFile (usually (TC depending): contplug.ini) configurable texts and size definitions.


Regards

J.Bl

[Vansumsen]

To J.Bl.
Thanks for this new version.
This version works fine for my configuration.

Suggestion for the french language in the contplug.ini

Code: Select all

[ImgSizeContentPlugin]
TextLanguageNo=3
TextLandscape=Landscape|Querformat|Paysage
TextPortrait=Portrait|Hochformat|Portrait
TextSquare=Square|Quadratisch|Carré
TextSmall=small|klein|Petit
TextMedium=medium|mittelgross|Intermédiaire
TextLarge=large|gross|Grand

Just one little thing... I deplore that a full translation oblige the user to adapt two files... the "contplug.ini" in TC folder and "imgsize.lng" in the imgsize folder... it is not an easy way for a commun user !
It would be easyer if all translations would be into the same file: the "imgsize.lng".
This is just a wish !

Friendly
Paul

[Clo]

2J.Bl
Hello !

Done.

Sorry, not found till this moment…
¤ Please, could you resend it ? Thanks.

 K R
Claude
Clo

[Clo]

2Vansumsen
Hello Paul !
¤ Like you can see in my previous posts here, I've some problems with that plugin under Win 98 SE…
- I checked : I have not any <contplug.ini> in the TC-dir.
- But yet, I have other content-plugins installed which work…

Any idea ?

 Friendly,
Claude
Clo

[J.Bl]

2J.Bl
Hello !

Done.

Sorry, not found till this moment…
¤ Please, could you resend it ? Thanks.

Done (to charriesATwanadooDOTfr with subject TOTAL_COMMANDER as you requested) a second time.

The contplug.ini file is AFAIK - if it is not yet existing - generated by TC (not by the Plugin itself) as the standard Content Plugin ini file in the moment, when it is needed (... when colums from the spezific plugin are shown).

Regards

J.Bl

[J.Bl]

Hello,

To J.Bl.
Thanks for this new version.
This version works fine for my configuration.

Thank you. You'r welcome.

Suggestion for ...

... my 'perfect' translations to ...

... the french language

Done. Thank you for your support.

Just one little thing... I deplore that a full translation oblige the user to adapt two files... the "contplug.ini" in TC folder and "imgsize.lng" in

Yes, I do the same. But - I'm sorry - AFAIK the Plugin has no nothing information about the file 'imgsize.lng' (the name, the path... and no informations about the path of the Plugin 'imgsize.wdx' itself...) and moreover no nothing informations about the actual used language in TC. The translations from this file 'imgsize.lng' are - transparent for the plugin - done by TC itself and can only be used for column names. I tried to store some additional translations (small. medium, large...) to the 'imgsize.lng' file but it is not translated (... this is totally clear and correct). The file "contplug.ini" is the recommended ini file for content plugins. The name and path of it is published to the plugins from TC while startup. So I used it. I'm not very happy with this...

This is a Content Plugin Interface Feature Request to Christian:

- Something like a "translation sevice" called by the interface at startup of TC. Until sending words back to this new function, the interface will translate them in the actual used language based on informations stored in the language file 'xyz.lng'. (xyz=Pluginname)

and / or

- Something like a "language information function" called by the interface at startup of TC to inform the plugin about the actual used language of TC.

Regards

J.Bl

[franck8244]

AFAIK the Plugin has no nothing information about the file 'imgsize.lng' (the name, the path... and no informations about the path of the Plugin 'imgsize.wdx' itself...)

You can retrieve the path to your plugin then check for the lng file !!

[J.Bl]

You can retrieve the path to your plugin then check for the lng file !!

With the TC Content Plugin Interface, which is recommend to use, how?

Regards

J.Bl

[franck8244]

I do not know if this will work with content plugin:
With delphi 6, this is how I do it :

Code: Select all

var
path:String;
begin
...
SetString(path,ModName,Windows.GetModuleFileName(HInstance, ModName,SizeOf(ModName)));
path:=ExtractFilePath(path);
...

this way you'll have the path to your plugin directory

[J.Bl]

I do not know if this will work with content plugin: [...]

However, is there an information about the actual used language in the TC content plugin interface? This is one of the questions. One another, are there no interface functions for translations of _content_ in the content plugin interface of TC and the plugin has to handle it by its own?

Regards

J.Bl

[franck8244]

Maybe you can search in TC ini file the Mainmenu value under the configuration section

If present, it should be something like WCMD_XXX.mnu and you'll have to extract XXX

After that you can search the XXX section in your lng file

[J.Bl]

Maybe you can search in TC ini file the Mainmenu value under the configuration section

If present, it should be something like WCMD_XXX.mnu and you'll have to extract XXX

After that you can search the XXX section in your lng file

This will often not work...

Regards

J.Bl

[Hacker]

You could also try and look for LanguageIni=...

HTH
Roman

[J.Bl]

You could also try and look for LanguageIni=...

HTH
Roman

Yes. "franck8244" is thinking about the same ini elements...

But this will often not work... (for example in my configuration)

Regards

J.Bl

[Clo]

2J.Bl
Hello !
- I got the test-library, thanks ! You can see the result in the window on that screen-shot

The contplug.ini file is AFAIK - if it is not yet existing - generated by TC

- Obviously, it is not created @ home ! Maybe that file is created only when these plugins are installed via the built-in feature of TC? I don't use this, but TC Plugman to install all plugins.

 VG
Claude
Clo