Creating an epub from indesign does not work with kindle because fonts are not embedded

According to a post on the web. It says the following:

And to round off this subject, it's possible to embedd fonts for Kindle devices. First export the EPUB file from InDesgn with the fonts embedded. After generating the EPUB file, crack it open (I use Oxygen XML Editor or Author XML Editor for this). Simply delete the 'encryption.xml' file located within the META-INF folder. Then you must replace all the fonts within the Fonts folder with the unencrypted versions. The fonts within the EPUB file are enctypted, so they cannot be read.

That's all there is to it. Open the file with Kindle Previwer and you will see the fonts in use. Keep in mind that iBooks overrides some HTML tags with the font selected by the reader, so your embedded fonts won't work for all text on that plattform. For example <h1> tags work, but <p> tags don't.

Most importantly, don't do this unless you own the font, have purchased a font license, or are using an font that allows you to freely embed it.

Good luck!

Not sure if it would work for reflowable 

You are using three elements in combination that don't work well at all, regardless of how the EPUB is constructed. Very little of it is InDesign's fault, at least not directly.

EPUB is not a rigidly enforced standard. A vast amount of success or failure or just outcome depends on the reader, which is free to interpret the EPUB code any way it likes, and, for many readers out there, does so following the whim of the programmer. So you have little to no control over what an EPUB user (== human reader) sees unless you demand they use a specified reader. While Kindle does enforce a single reader (and a somewhat more rigorous standard), much of the same is true when you go outside some basic limits.

The first problem is that fixed-page EPUB, FXL, is an old, poorly implemented and problematic format. It should not be used except for a very limited number of  book types that are mostly "picture page" types, and never for mostly-text layouts. (If you want perfect replicas of print pages... use PDF.)

The second problem is that font embedding has always been somewhere between tricky and glitchy in EPUB. It works for some readers, but not others. It can be fussy about what fonts it works with, over and above the issue of those fonts needing to be licensed for e-book export. (Most are if encryption is supported — that is, the font files are encrypted so that they can't be extracted and used on their own.) And in the end, most readers give their own font preferences and the user settings (for font size, face, spacing, etc.) priority over how the book pages are encoded.

The third problem is that Kindle is "yet more of the same" and is very resistant to specified fonts, giving great preference to using its own system fonts and user settings.

So three strikes, yer out, here. The preferable method for e-books in 2024 is to use reflowable layout, learn methods for controlling page layout within that 'liquid' model (it can be done) and not to specify or embed fonts at all.

As for "InDesign not embedding fonts," I suspect you'll find the fonts are indeed embedded in the file — the FXL layout more or less requires them to be there — but that it's the readers that are ignoring them. If you are trying to use fonts that don't contain a licensing tag for e-book export, those would be refused, but you'd see error messages on export.

InDesign has its flaws and limits on EPUB creation but is probably the best layout-based tool there is for creating e-books. But there are so many other factors in play that working around ID's few limits is the easy part of successful EPUB/Kindle creation.