Right now, rtfd files that we use for the Mac installers are manually generated. Any change in these files need to be manually done which poses an issue for the localization team. We have to send the english strings and then manually create rtfd files for localized strings returned from the i18n team.
This change should create rtfd files automatically for each supported i18n language at build time by pulling in information from the Localizable.strings files at build time.
Auto generate Welcome and Conclusion html files with using text from strings or properties files.
Then lets go this way. As a side Q - Can we implement accessibility bugs (the ones we closed) when we switch to html? i.e. Does the html format support for better accessibility? Can you also test/check this?
Yes. The current PackageMaker tool supports HTML files files as well.
Does the current tool (packagemaker) support HTML files? If yes, I am okay with changing *.rtfd to *.html
The new tools from Apple (pkgbuild, pkgutil and productbuild) which replaces the PackageMaker does not accept RTFD for Welcome, Read-me, License and Conclusion. Instead of auto generating the rtfd files, auto generating HTML files will be a better idea, keeping in mind that switching to the newer Apple tools for creating installation packages.