On Wed, Jun 20, 2018 at 10:48:47AM +0300, Liudmila Mantrova wrote: > To complete the picture of possible issues with older branches in XML, we > posted a question in packager lists some time ago and didn't receive any > objections. Just to keep record of all related questions in one place, here's > the link: > > https://www.postgresql.org/message-id/flat/ > 06efc906-16f8-0cde-5bee-e3d5abfc00ba%40postgrespro.ru# > 06efc906-16f8-0cde-5bee-e3d5abfc0...@postgrespro.ru > > We totally understand the reluctance to volunteer personal time for manual > testing of legacy branches - sad as it is that we may miss some benefits of > the > previous efforts. E.g. all styles and transforms have been stabilized for > version 11, so they could be reused for older branches. As for testing the > content conversion, our scripts can handle it in a fully automated way by > comparing the original and the final outputs via the .txt format, so all > possible differences will be caught. > > It's unfortunate that we'll have to deal with different formats in the > supported branches for several more years, but we at Postgres Professional are > ready to accept any your decision on this matter for now.
I had not thought of translations, but wouldn't all translations also need to switch from SGML to XML for back branches? That would be a lot of work. -- Bruce Momjian <br...@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + As you are, so once was I. As I am, so you will be. + + Ancient Roman grave inscription +
