Preliminary information about Unicode support (TC7.5)

[fenix_productions]

2ghisler(Author)
Are there any chances to provide sample Unicode plugin with ft_string, ft_stringw fields?

What about ft_fulltext? Does it also support Unicode?

SDK help file says that length of returned value is maxlen-1 in that case. How is it reflected in Unicode case? Half of it for UTF-16?

[ghisler(Author)]

You can return either ft_string or ft_stringw, Total Commander will accept both for one string field. Just make sure to test for the version number of the plugin interface before returning ft_stringw.

There is no ft_fulltextw at this time, sorry.

[fenix_productions]

2ghisler(Author)
For standard plugin I can return ft_string like:

Code: Select all

//tmpval as std::string
strlcpy((char*)FieldValue, tmpval.c_str(),maxlen-1);

How to do that for Unicode?

Will it be correct for ft_stringw?

Code: Select all

//tmpval as std::wstring
wcscpy((wchar_t*)FieldValue, tmpval.c_str(),maxlen-1);

I think I will wait for more samples

[ghisler(Author)]

Yes, when you return a Unicode string, return ft_stringw.

However, the correct copying call is like this:

Code: Select all

wcscpy((wchar_t*)FieldValue, tmpval.c_str(),maxlen/2-1);

Note the /2 because "maxlen" is the size in bytes, not in characters for any type of field.

[Postkutscher]

2ghisler(Author)
When the new plugin writer`s guide will be available?

[ghisler(Author)]

I will make an announcement shortly here in the plugins forum.

[Postkutscher]

Here it is. I see.

Thank you!

[Lefteous]

2ghisler(Author)

There is no ft_fulltextw at this time, sorry.

Any news on this?

[XPEHOPE3KA]

2ghisler(Author)

There is no ft_fulltextw at this time, sorry.

Is this planned for 9.0 version maybe?

[ghisler(Author)]

Yes, ft_fulltextw has been added in November 2014(!). Unfortunately I just can't release TC9 yet because the expectations are too high. There is still a lot to add.

[milo1012]

Yes, ft_fulltextw has been added in November 2014(!).

That's great to hear!
Is the encoding in UTF-16 or UTF-8 format?

Also, as I already suggested here:
Is it possible to add all wdx fields with full text search to the search dialog's main tab?
It would make an easier access, and shows the user some alternate engine immediately.

[Lefteous]

2ghisler(Author)

Yes, ft_fulltextw has been added in November 2014

Great!

2milo1012

Is it possible to add all wdx fields with full text search to the search dialog's main tab?

As far as I understood this should be part of the already confirmed features for TC 9.
http://www.ghisler.ch/board/viewtopic.php?p=297896#297896

[tbeu]

Does this mean the WDX API version was incremented?

[milo1012]

As far as I understood this should be part of the already confirmed features for TC 9.
http://www.ghisler.ch/board/viewtopic.php?p=297896#297896

Yes, but I think we need to see this in action.
Judging from the description it seems to be combined with Office/XML search, which might not exactly be what I meant.

In any case, good to see progress in this matter.

[Lefteous]

2milo1012

Yes, but I think we need to see this in action.

Sure.

Judging from the description it seems to be combined with Office/XML search, which might not exactly be what I meant.

It somehow must be 'combined' with 'Office xml'. There must be some kind of mechanism how to search for file contents. If you want to search text in docx files you have to define if you want to use the internal mechanism or for example using the "TextSearch" plugin.