Hello! On Thursday 17 October 2019 09:50:08 Pali Rohár wrote: > On Wednesday 16 October 2019 16:33:17 Sasha Levin wrote: > > On Wed, Oct 16, 2019 at 06:03:49PM +0200, Pali Rohár wrote: > > > On Wednesday 16 October 2019 10:31:13 Sasha Levin wrote: > > > > On Wed, Oct 16, 2019 at 04:03:53PM +0200, Pali Rohár wrote: > > > > > On Friday 30 August 2019 09:56:47 Pali Rohár wrote: > > > > > > On Thursday 29 August 2019 19:35:06 Sasha Levin wrote: > > > > > > > With regards to missing specs/docs/whatever - our main concern with this > > > > > > > release was that we want full interoperability, which is why the spec > > > > > > > was made public as-is without modifications from what was used > > > > > > > internally. There's no "secret sauce" that Microsoft is hiding here. > > > > > > > > > > > > Ok, if it was just drop of "current version" of documentation then it > > > > > > makes sense. > > > > > > > > > > > > > How about we give this spec/code time to get soaked and reviewed for a > > > > > > > bit, and if folks still feel (in a month or so?) that there are missing > > > > > > > bits of information related to exfat, I'll be happy to go back and try > > > > > > > to get them out as well. > > > > > > > > > > Hello Sasha! > > > > > > > > > > Now one month passed, so do you have some information when missing parts > > > > > of documentation like TexFAT would be released to public? > > > > > > > > Sure, I'll see if I can get an approval to open it up. > > > > > > Ok! > > > > > > > Can I assume you will be implementing TexFAT support once the spec is > > > > available? > > > > > > I cannot promise that I would implement something which I do not know > > > how is working... It depends on how complicated TexFAT is and also how > > > future exfat support in kernel would look like. > > > > > > But I'm interesting in implementing it. > > > > It looks like the reason this wasn't made public along with the exFAT > > spec is that TexFAT is pretty much dead - it's old, there are no users > > we are aware of, and digging it out of it's grave to make it public is > > actually quite the headache. > > > > Is this something you actually have a need for? an entity that has a > > requirement for TexFAT? > > Hi! > > I do not have device with requirements for TexFAT. The first reason why > I wanted to use TexFAT was that it it the only way how to use more FAT > tables (e.g. secondary for backup) and information for that is missing > in released exFAT specification. This could bring better data recovery. > > > I'd would rather spend my time elsewhere than digging TexFAT out of it's grave. > > Ok. > > I was hoping that it would be possible to easily use secondary FAT table > (from TexFAT extension) for redundancy without need to implement full > TexFAT, which could be also backward compatible with systems which do > not implement TexFAT extension at all. Similarly like using FAT32 disk > with two FAT tables is possible also on system which use first FAT > table. By the chance, is there any possibility to release TexFAT specification? Usage of more FAT tables (even for Linux) could help with data recovery. > > Is there anything else in the exFAT spec that is missing (and someone > > actually wants/uses)? > > Currently I do not know. I found one missing thing: In released exFAT specification is not written how are Unicode code points above U+FFFF represented in exFAT upcase table. Normally in UTF-16 are Unicode code points above U+FFFF represented by surrogate pairs but compression format of exFAT upcase table is not clear how to do it there. Are you able to send question about this problem to relevant MS people? New Linux implementation of exfat which is waiting on mailing list just do not support Unicode code points above U+FFFF in exFAT upcase table. -- Pali Rohár pali.rohar@xxxxxxxxx
