Why require XML knowledge to write an Apple Book?

Question

Level 1

4 points

Why require XML knowledge to write an Apple Book?

I'm looking at publishing some woodworking techniques on Apple Books. In https://help.apple.com/itc/booksassetguide/en.lproj/static.html, the Apple Books Asset Guide 5.3.1, there's a huge emphasis on knowing XML, XHTML and CSS in order to produce an EPUB book. Well, it's good to know that the font should be 3% of the page height, but MS Word, LibreOffice and Pages (which I don't use) still specify font in points, not in em or px that I can see. I can't see where that document recommends the page size in inches or mm, or the margin size, or the font size. I was able to publish a textbook through Springer-Nature with such basic information. Some of my U.S. Patents required using USPTO Word templates, but it was doable. I see no Word, LibreOffice or Pages templates for an Apple Book.

If the object is to sell more good books, how does it profit Apple to erect such a thorny technical barrier to people who don't write in computer languages? Would it not create more business to instead provide basic templates on, and instructions, for common word-processing packages? Or does Apple prefer to drive that business to Kindle?

Posted on Nov 16, 2025 11:33 AM

Reply

Answer 1

Tom Gewecke

Level 10

121,938 points

Nov 21, 2025 7:40 AM in response to dbaker586

dbaker586 wrote: Your response, still doesn't address the basic lack of published document standards which are readable to someone not versed in XML, XHTML and CSS.

Sorry about that, but in these forums you are only talking to other users like yourself, who volunteer to try to help solve problems, and nobody here can address the standards issue you raise. To make your points to Apple, you need to use the feedback link provided earlier.

For people who use Word, the best solution to producing books for Apple's store is often to go through a Partner (link provided earlier), which shifts the burden of compliance with Apple's standards from you to them.

Reply

Answer 2

Nov 21, 2025 7:44 AM in response to dbaker586

Are you creating apps to create an EPUB using the Apple Books EPUB format, or apps to verify or pre-flight an EPUB? If so, those EPUB file format specifications are for you.

If you are however looking to create an EPUB version of an article, use your preferred EPUB-capable app (such as Pages or Affinity Publisher or LibreOffice or whatever), and select EPUB as the export format.

Reply

Answer 3

Tom Gewecke

Level 10

121,938 points

Nov 22, 2025 7:57 AM in response to dbaker586

dbaker586 wrote: After decades of using Word

I see that LibreOffice offers an option to export fixed-layout ePub. Have you tried importing your Word stuff into that and converting to epub there? I have no idea if it meets Apple's requirements, but better than Word which does not export to epub at all.

Reply

Answer 4

Tom Gewecke

Level 10

121,938 points

Nov 20, 2025 8:15 PM in response to dbaker586

dbaker586 wrote:

That means fixed-form pages, not flowing text.

Apple's Pages has these fixed-form templates on my machine:

Reply

Answer 5

dbaker586 Author

Level 1

4 points

Nov 20, 2025 7:18 PM in response to Tom Gewecke

I don't want to write a documentary or a story, but a technical woodworking article, with plenty of figures. That means fixed-form pages, not flowing text. It has to look good at least on a 10.5-inch iPad Pro (like mine). So instead of finding useful and concise information on how to scale the work on a page, for example, Apple gives me a hundred-page treatise on XML programming and EPUB standards - which I have no interest in learning. Being old and on my second cancer, life is way too short to wade through all that, not to mention tiring.

So, no help from Apple, just a long slog through trial and error. I miss CreateSpace. Unfortunately, Amazon bought them out and promptly lost my first book, which I also prepared in Kindle format.

Reply

Answer 6

dbaker586 Author

Level 1

4 points

Nov 21, 2025 7:25 AM in response to Tom Gewecke

I don't use Pages for the same reason that I still use a QWERTY keyboard. After decades of using Word and Word-like document processors, switching to someone else's favorite system is a horrible pain in my muscle memory. So whatever Pages does in this case is irrelevant.

Your response, repeating yourself, still doesn't address the basic lack of published document standards which are readable to someone not versed in XML, XHTML and CSS. If you look around the publishing industry, you may find that other publishers' Instructions to Authors are easily found, concise, informative and readable to anyone using any word processor.

The fact remains that Apple's approach to describing how to publish a book in Apple Store, intentionally or not, raises a barrier to all of us who were not original Apple users. It seems entirely unwilling to teach or reach anyone not already Truly Apple.

Personally, I'm already struggling with disabling health conditions. Now I have to consider whether or not I should even bother to write the article.

Reply

Answer 7

Tom Gewecke

Level 10

121,938 points

Nov 16, 2025 4:07 PM in response to dbaker586

dbaker586 wrote:

I see no .. Pages templates for an Apple Book.

I have no problem seeing a lot of them in Pages > File > New, as partially shown below.

Pages if of course the app specifically designed to produce books for Apple's store. If you have problems with 3rd party apps, probably best ask in their own forums. Many authors use "Partners" to help make their stuff work right for Apple's store:

https://itunespartner.apple.com/books/partners

To let Apple know how you would like their book publishing system improved, you can use

http://www.apple.com/feedback

Reply