DOM API v. Generator API

We have a project where we are generating PDF files from scratch and are interested in using Aspose.Pdf as the engine for creating these documents.  In reading through your documentation, How to Use New Aspose.Pdf for .Net API it reads to me that the new DOM model is for modifying existing Pdf files while the older Generator model is still the API set used to create Pdf documents from scratch.

Aspose.Pdf.Generator

The old Aspose.Pdf for.NET (pre-6.0) provided the features to create new PDF file from scratch. As we have merged old Aspose.Pdf and Aspose.Pdf.Kit, all the classes previously available in old Aspose.Pdf for .NET have been moved under the Aspose.Pdf.Generator namespace. So, if you want to execute the old Aspose.Pdf code using the new product, use this namespace


Is this still the case that if I am generating documents from scratch I should be using the Generator API set?  If yes then I'm very concerned with regards to the last comment made to a issue I submitted in PDFNEWNET-35284, that the Generator is legacy and you are no longer being enhanced or corrected, aka not supported.  I need to know now if all this is accurate because I know of at least one enhancement we would like (ability to apply our own footnote label rather than have them automatically generated/numbered) and I know we would want corrections made if we were to encounter bugs.

Thanks,
Tim