The characters "U+200E" and "U+200F".

[ANACOSTIA]

Select files --> "File" --> "Copy Property" --> "Copy as TSV".
This tsv file includes characters "U+200E (LEFT-TO-RIGHT MARK)"s and "U+200F (RIGHT-TO-LEFT MARK)"s at "Date Modified", "Date Created", etc.
Can I get a tsv file not including "U+200E"s and "U+200F"s?

[void]

Thank you for the issue report ANACOSTIA,

When using Copy as TSV, Everything formats dates as:

yyyy-MM-dd HH;mm:ss

by default.
No LTR and RTL markers are added.

Please send your Help -> Troubleshooting information in a bug report.

Please send a sample TSV file with RTL markers in a bug report.

[ANACOSTIA]

I have attached the files.
In example.tsv.txt file, the column order is "folder path", "file name", "Date Created", "Date Modified", "Date Content Created", "Date Saved", "Date Printed".
This file includes "U+200E"s and "U+200F"s.

[void]

Thank you for the troubleshooting information and sample TSV.

You are indexing Windows Property System Properties.
It is System.Document.DateCreated, System.Document.DatePrinted, and System.Document.DateSaved that have LTR markers.
These markers are added by the system (not Everything)
The next Everything update will tell the system not to add these LTR markers when exporting or copying as TSV.



For now, please use the following Everything properties instead:
Date Content Created (pulls values from System.Document.DateCreated)
Date Printed (pulls values from System.Document.DatePrinted)
Date Saved (pulls values from System.Document.DateSaved)

Everything doesn't add LTR markers to Everything properties when exporting or copying as TSV.

[Herkules97]

Why not keep the LTR markers for the WPS property? If it was just a case of using the WPS version of things.
Then I presume you get a more raw version if you use the WPS version and more readable version if using the EBV version?

[void]

Why not keep the LTR markers for the WPS property?

Everything uses LTR markers when displaying and will continue to do so.
They shouldn't be used when exporting.

Everything also uses LTR markers for Everything properties when displayed.

Then I presume you get a more raw version if you use the WPS version and more readable version if using the EBV version?

The system formats the WPS properties.
I don't have a lot of control here.
Generally, Everything properties and WPS properties display the same.



For a more technical answer, Everything uses IPropertySystem::FormatForDisplayAlloc to format WPS properties for display.
For the next Everything update, Everything will use PDFF_NOAUTOREADINGORDER when exporting (or copying as TSV).

[Herkules97]

For the next Everything update, Everything will use PDFF_NOAUTOREADINGORDER when exporting (or copying as TSV).

It says there are still some values that keeps LTR markers, so I searched for it and Google AI Summary claims some stuff and links to..
https://github.com/microsoft/Windows-cl ... SOleDB.cpp
Is this something you'd use to implement the new one? Just curiosity, I have no practical use for this information.
Cause it has..

hr = ppd->FormatForDisplay(propvar, PDFF_NOAUTOREADINGORDER, &pszValue);
if (SUCCEEDED(hr))
{
// Strip remaining order reading marks from the string:
// LRM RLM LRE RLE PDF LRO RLO
_StripCharacters(pszValue, L"\x200e\x200f\x202a\x202b\x202c\x202d\x202e");

Which looks like if the string still comes with them, the AI claims datetime modified is one of the values, this would remove them entirely.

Seems a bit weird for Microsoft to use this sort of workaround if they developed the original PDFF_NOAUTOREADINGORDER.

[void]

I will stick with just PDFF_NOAUTOREADINGORDER for now.
I'm not seeing any WPS properties use LTR markers with this flag.

I would like to avoid manually stripping these LTR markers.
Everything will export the WPS property text as the system returns it.