I understand that ghostscript can convert texts fonts to outlines with the option -dNoOutputFonts. You may run that before importing into Mathematica.

cairo was not (originally) a page description language: it was a vector graphics language for programs to make vector graphics in X Windows only when x.org was in use. Postcript was developed in BELL LABS for X and printers both to use (it's a 2D language not 3D) (as i said, cairo is a rip-off of postscript per say but was easier to program in and had more features). printers and postscript did not support it cairo (initially) - and driver support in (linux) was a hairy issue.

perhaps your system has a cairo <> postscript converter that is GPL. very like, if so, IT HAS ALLOT OF BUG that anyone who is to the em would not appreciate. that would mean you would never get "justice" if you wanted exact output using "eps" or "ps" you could take a fine ruler to. GPL software does get hacked by "mal contents" (including competitors to Wolfram Mathematica) ... a thing which is just un-avoidable.

i'm unsure if PDF uses cairo - but it might not. if it doesn't - try that

my upshot here is avoid the whole situation by not using any of it if possible

personally i expect a math program to have output one can use and engineering slide rule with. in today's IT environment that might be too much to expect since people just wreck stuff they have no idea about

my upshot here is avoid the whole situation by not using any of it if possible

there are many reason why you may never "get justice" and should "try another way that doesn't involve EPS or maybe even PS either

I don't have time to test this but I do know basic postscript programming.

As the person above said: save a simple Mathematica plot (it has text) then hit Ctrl-Shift-e you'll see the postscript (eps) code. (it works, your other software is not working)

The plot will import and export (there is a few minor bugs with line width for tables in some cases).

The EPS is both Adobe (paid use non-free) and Mathematica postscript code, in the postscript programming language. PDF is similar but newer version and is (partly) compressed (you can't see all the code without finding the right de-compression).

The Mathematica postscript in each .ps or .eps does two things:

(1) it provides the postscript programming for using Mathematica fonts (for loading them, naming them, scaling them - ie for radical verticuland width, printing them at the right width). you have to have those fonts installed on the system or you won't see them in GhostScript. they are copyright wolfram your not allowed to "share them" (if you bought mathematica there are instructions for installing fonts for ghostscript to make use of for the purpose of printing)

(2) it provides basic functions for doing plot lines and such (in the ps programming language, with frames of total width and units - which is a new bug sometimes the total width is wrong so the line width gets multiplied wrong). i'm unsure when and if what ps functions go automatically in every .eps - but there will be some in there. typical ps functions do things like check plot range and plot scale and generate tick marks for axis based on scale. for example this would be in an EPS:

(0.5)Tj
(is some text)
Tj is a wolfram function that ads postscript code as to the font and placement of the text

actually i see wolfram has "lifted" gpl'd cairo borrows from linux libs (that's probably both un-necessary and probably why it's has new bugs. but i'd have to check if adobe has released it's own cairo. cairo was originally a rewrite of postscript graphics for X that "stole postscript" and extended it's vector abilities which in turn could be used on the X desktop with X.org - but many no longer support x.org because of many many reasons)

I don't understand too much about this things. Normally I use the Mathematica-generated EPS-Files with LaTeX or somtimes with inscape or Ghostviewer to dieplay them. And there was no problems at all.

Only Mathematica itself make trouble with importing its own files.

After your hint I looked up a little bit for "Character Encodings". The Standard is WinowsANSI, but there seems to be an option to change this with exporting and importing. So I tried this:

Graphics[Text["A", {0, 0}]]
Export["image.eps", %, CharacterEncoding -> "UTF8"];
Import["image.eps", CharacterEncoding -> "UTF8"]

But it doesnt help, same problem like before. I don't know if this option had some effect on the output-file.

I make now a workaround: I export and import the file as PDF and export the graphic with the inserted PDF at the end as EPS.

Thank you for your hints!

Attachments:

image.eps

Yes sure, I only thougt that Export["image.eps",Graphics[Text["A", {0, 0}]]] produces the same file for everybody. But perhaps I might be wrong.

Attachments:

image.eps

The EPS is generated with mathematica with Export[], see the code above. Does the code above work for you?

As written above there is no error-message, mathematica keeps running and cannot be aborted anymore.

I use Windows 10 and Mathematica 12.