Open rezanid opened 1 year ago
I'm with you for resx files.
But why would you want office files to display the raw xml?
And if I'm not mistaken office files are actually zip files that contain xml files and not xml files themselves.
I am a developer and some times I have to work with several different kinds of XML files. In case of Office, I have a tool novodocx ;) that I maintain here in Github. I need to get to the low-level file structure. Being able to preview would mean I don't need to always open the file to see what's in it. I think other developers would appreciate the ability to add more extensions for XML and maybe also for text preview.
Also interested in a customized configuration of extensions, to map to XML, code and plain text. There are lots of small files that should be recognized or configurable. The max size 50 KB is maybe a bit low. Perhaps take and show the first 50 KB?
<?xml
and max size)
.props
.target
.ruleset
.shfbproj
.pubxml
.nuspec
.resx
.cd
.sln
.svc
This also applies to some files being just text files internally. It would be useful, to specify a list of file extensions which should be treated as .txt files.
If you just want a text preview in Explorer, add a registry entry mark it as text. For example, I have a lot of .NFO files (no, not System Info files, which are just XML text)... so adding a PerceivedType
REG_SZ and setting to text
will work.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\.nfo]
@="NFO File Descriptions"
"Content Type"="text/xml"
"PerceivedType"="text"
If you just want a text preview in Explorer, add a registry entry mark it as text. For example, I have a lot of .NFO files (no, not System Info files, which are just XML text)... so adding a
PerceivedType
REG_SZ and setting totext
will work.Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\.nfo] @="NFO File Descriptions" "Content Type"="text/xml" "PerceivedType"="text"
Thanks for the suggestion! I would consider it as a workaround though. Because every time we need to add a new extension we will need to modify the registry value. Also aren't there any side-effects? Does it affect the file extension association or the icon for example?
Description of the new feature / enhancement
There are several file formats that internally they are just XML (.resx). It would make sense to allow the end-user to add custom extensions and ask the plugin to treat them as XML.
Scenario when this would be used?
There are many file formats that are based on XML. Currently these files cannot be previewed. Office files, .resx files are just a few examples.
Supporting information
No response