This bug is intended to track the evaluation of UDF support in xorriso.
The goal is to (re-)use existing building blocks instead of reinventing
the wheel once again. Whether or not it will be supported is unclear yet.
So far I can see signs of UDF support in:

udftools - should split a shared library.
libcdio - read-only support.

It might turned out that leaving the UDF (read-write) support to udftools
would be more appropriate.

I understand that UDF is completely different from ISO9660 and I don't expect fine-level editable UDF support to be implemented in xorriso. Perhaps some different program could be made for this, but it would be good to have DAO (disc-at-once) UDF support at least.

genisoimage already has it, but it is unmaintained since - what was it - 2010?  And it is showing: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=990468;msg=7 (the 2027 date bug)

The good things about UDF are longer file name limits on Windows and longer volume label limits. Though from my testing, ISO9660 has a lower file system overhead, so it would be preferrable for many small files (tens of thousands).

UDF 1.02 is enough for DAO purposes. Anything after that is mainly for stuff like packet writing / live file system.

Hi,

it is not planned that libisofs will ever support UDF. So libisoburn
will not be able to produce UDF.

As for the Y2027 bug in genisoimage, this is a problem which should be
fixed there. genisoimage not only does UDF but also prepares images for
video DVD, which is out of the scope of libisofs, too.

The main obstacle for a fix in genisoimage is its lack of a Debian
maintainer.
One would have to prepare a patch like those in
https://sources.debian.org/src/cdrkit/9%3A1.1.11-5/debian/patches
and then talk e.g. debian-mentors mailinglist into helping to bring
this patch into the cdrkit package.


Have a nice day :)

Thomas