Publisher Files
How to Test a Publisher Replacement with Your Own Documents
Use real publications to test editing, import fidelity, saving and printing before switching. Record failures and choose a workflow that fits your documents.
5 min read
27 September 2026
Test a replacement with a small set of your own representative publications. Check ordinary editing tasks, imported layout, saving and reopening, then physical output. Record what works, what needs correction and what cannot be reproduced. A feature list or attractive demo is not a substitute for that evidence.
Turn your regular work into test cases
List the jobs you actually repeat. Examples include updating a menu price, replacing a newsletter photograph, making a two-sided flyer and adapting a card for another name. Give each task a clear success condition that somebody else could observe.
Separate essential features from preferences. If you never use a specialist Publisher feature, its absence may not affect your work. If a particular fold, form or print measurement is critical, treat it as an acceptance gate. Avoid scoring every feature equally merely because it appears in a comparison table.
Choose samples that expose the difficult parts
Use copies and remove private data where it is not needed for the test. Keep a PDF or screenshots from the original application as a reference. If you cannot obtain a reference, state that visual fidelity is only partly verifiable. A plain page that passes quickly should not stand in for the whole archive.
- One ordinary single-page publication used frequently
- One dense text layout with tight frames
- One multi-page publication
- A design with cropped, rotated or flipped pictures
- A document using unusual fonts or symbols
- A folded or exact-size print job if that matters
- One file that has caused problems before
Test editing, not only opening
Change a heading to a longer sentence, replace a picture and adjust a price. Select part of a sentence and apply the intended formatting. Move and resize an object, then undo. These small tasks reveal whether the recovered content behaves like useful editable objects or a collection of difficult fragments.
Repeat the important tasks after saving and reopening the project. Record any content that remains an image instead of text, or any object that requires reconstruction. Do not label a file fully editable because one heading can be changed.
Compare layout systematically
Begin with page dimensions and orientation. Then compare large panels, text, images and object order. Zoom out to see composition and zoom in to read detail. If a whole page is consistently displaced, investigate geometry before individually moving dozens of objects.
Record differences as observations: “page two’s body text wraps three lines earlier” is useful; “layout bad” is not. Check font availability and substitutions before adjusting text-frame geometry. Test with the fonts and printers that the actual user will have.
Give printing its own acceptance check
Preview all pages and print a small proof if the work is intended for paper. Measure a known dimension. For folded work, assemble a dummy; for labels, check alignment against the actual stock. Test both sides where required, because duplex orientation and page order are not established by a one-sided preview.
Record the paper, printer, driver options and scaling used. A repeatable configuration is more valuable than one unexplained good print. If your job goes to a commercial printer, ask that printer to assess a sample against its requirements.
Use a simple decision record
Include the source identifier, application version, test date, reviewer and time spent repairing. A correction that takes five minutes on one file may be acceptable; the same correction repeated across thousands of pages changes the decision.
- Pass The task works and the output meets its acceptance condition.
- Pass with a documented correction The result is usable after a repeatable adjustment whose cost is understood.
- Needs investigation The result is inconsistent or there is insufficient evidence to accept it.
- Does not meet the requirement An essential task or output cannot be achieved through the tested route.
Apply the same test to RemPress
RemPress provides a Windows workflow for everyday page layouts and supported PUB recovery. Use the browser converter with a sample, inspect the notes and test the downloaded project in the application. Check current features and requirements rather than assuming every Publisher function is included.
Keep commercial evaluation on the Publisher Alternative page; use this guide as your evidence checklist. If a sample exposes a specific issue, send support a reproducible description and agree an appropriate way to share any necessary file.
Review RemPress as a Publisher alternative
Make the decision against your essential tasks
Choose a workflow when it meets the jobs you need at an acceptable correction cost. You may use one route for editable masters and another for historical reading copies. Record unresolved cases and retain the original archive until they have a clear plan.
Repeat the relevant tests after a significant application update or a change of printer. You do not need to retest everything for every small edit, but any change affecting an essential part of the workflow deserves a targeted check.