No, in that case I tried to open a file from a BFS volume, as I thought about it as this treat how would it be working in Haiku …
/SANDSK256GO is a full BFS volume on a thumbdrive.
I plugged in an exfat thumbrive – mounted read-only.
(I have CVs there which should be .docx files I do not have EXCEL files so much - saved. I should might find some on an older drive that can contain some of templates from my IT guy era. I had not felt to store infos in excel files for personal stuff.)
Well, in this case detection went well, I assume as on non-BFS volume Tracker fallback to extensions.
but Libreoffice could not open the file
as I have HUN localization - with non-English latin letters - folder/file names there,
that Haiku does not treat the same way as Windows/Linux does -
it is experience, not assumption !
You can see it in the error message window,
Cannot handle ../Önéletrajz/.. folder which was created on Windows earlier.
(that means autobiography, in Hungarian - we use the same word for CV as well, we do not have an another word to differentiate this condensed and work related type of autobiography, we may add ‘szakmai’ - so ‘professional’ autobiography if we want to differentiate)
Unicode on Windows/Linux and unicode on Haiku works a little different by default.
It was the same problem on Linux as well in the early 2000s years, but since then it changed. Not in all cases, but mostly.
Recently on one forum entry or in a Haiku ticket I met such terms as Unicode 8 and Unicode 16.
Haiku possibly use UTF8 by default, meanwhile Windows uses UTF16 … and may some Linux distros which ones wants to enable to use folders/files created by Windows – adapted to use UTF16 by default.
( Source Google Search to Unicode 8 Unicode 16 )
I am not sure, just guessing.
EDIT :
I copied the file - by dragging - to Desktop, so the filepath now was understandable for Haiku and the file was ‘Word document’ by type and opened in LibreOffice as expected.
So for issue resolution :
- → Haiku’s Terminal/Tracker should treat at least FAT/EXFAT/NTFS drives as UTF16 by default to work with their localized content – if my guessing is right.