Comment 1 for bug 1688353

Having strings that represent library policy statements bundled into a single resource file strikes me as something that would have been a reasonable design choice when TPAC was getting started, but the current approach is also a valid choice. Having the policy text split out keeps each part next to the context where the user is meant to read it, allowing for structural and design changes to be coordinated with changes to the text. For example, a library might elect to link out to a policy rather than quote it.

We're not starting with a blank slate, however; is there an argument to be made reducing the number of files to be edited by three (or so) is worth imposing a mandatory upgrade action?