1/ Postscript serves the same purpose than PDF but it just a lot less popular. (I removed PS export more than a year ago, I believe you are the first one to ask about it, if we would do the same with PDF, it would be instant).
2/ MuseScore already support PDF, SVG and PNG as graphical output. The most savvy users can create Postscript files from PDF or SVG if they really need a postscript file.
3/ One less feature is good for MuseScore. It's one more less element in the UI, less confusion for the users, one more less code path to maintain.
4/ Less support questions.
I'm curious how it looks in PostScript. PS files are text files and I can see where are bugs, etc., and I can edit files before printing, add or remove new pages, elements, etc. I have a problem with export to PS when I'm using external programs or ps/pdf printers.
Maybe I'm doing something wrong, but when I'm exporting to svg my multi-page scores are exporting to one page. Entire score is on one page... This is a bug or "property" of MuseScore?
SVG export has been implemented with a single page. Not sure why really. I guess it depends on the use case, some users might want a single page, others separated pages. Someone posted a feature request #21508: Export SVG file page by page, but there have been no discussion or other requests. The issue has been marked "by design". Not sure why either.
My feeling is that most users don't use SVG export and the ones who do use it are using it for short one pager.
Comments
I don't remember exactly why but I can think of good reasons to remove it. That's probably why I did it https://github.com/musescore/MuseScore/commit/c72816607d853a89dd4a250ae…
1/ Postscript serves the same purpose than PDF but it just a lot less popular. (I removed PS export more than a year ago, I believe you are the first one to ask about it, if we would do the same with PDF, it would be instant).
2/ MuseScore already support PDF, SVG and PNG as graphical output. The most savvy users can create Postscript files from PDF or SVG if they really need a postscript file.
3/ One less feature is good for MuseScore. It's one more less element in the UI, less confusion for the users, one more less code path to maintain.
4/ Less support questions.
Are they good reasons to keep postscript?
In reply to I don't remember exactly why by [DELETED] 5
I think the question goes along with gootector's desire to have OTF embedded in PDF?
In reply to I think the question goes by Jojo-Schmitz
I'm curious how it looks in PostScript. PS files are text files and I can see where are bugs, etc., and I can edit files before printing, add or remove new pages, elements, etc. I have a problem with export to PS when I'm using external programs or ps/pdf printers.
Maybe I'm doing something wrong, but when I'm exporting to svg my multi-page scores are exporting to one page. Entire score is on one page... This is a bug or "property" of MuseScore?
In reply to I'm curious how it looks in by Gootector
SVG export has been implemented with a single page. Not sure why really. I guess it depends on the use case, some users might want a single page, others separated pages. Someone posted a feature request #21508: Export SVG file page by page, but there have been no discussion or other requests. The issue has been marked "by design". Not sure why either.
My feeling is that most users don't use SVG export and the ones who do use it are using it for short one pager.
Regarding PostScript, I found the reason why it has been removed. It's not supported by Qt5 anymore. The Qt project removed PostScript support between Qt4 and Qt5 https://qt.gitorious.org/qt/qtbase/commit/34f712e79e97b757b4426e1ffa09e…