Start a new topic

More of the frequent Unicode characters in DOCX supported?

This is in MS-Word:


image


This is in CafeTran Espresso 2019:


image


That's nice!


Could this be achieved for frequent Unicode characters like these too?


image


image

It makes the text better legible in CafeTran Espresso 2019 and errows (= errors caused by swapping/misinterpreting arrows) could be avoided.


Users could come with suggestions for these frequent Unicode characters ...


And of course the number of tags could be reduced :).

As this depends on the font you are using, this would mean that CT needs to read out the special character including the font and if the character does not exist or is a placeholder in CT's font (= these funny squares above), CT uses the special font (Wingdings, Zapfbats or whatsoever) to display only these characters, but without switching the following characters to the different font. 


Sounds pretty complicated, but feasible, at least for native projects.

>Sounds pretty complicated, but feasible, at least for native projects.


Yes. That's why I wrote 'the most frequent' characters (some arrows, TM and Copyright symbol and the like, maybe about 15 or so).

> 'the most frequent' characters 


Clients do not care about choosing a certain font and symbol, I assume. Just checking with Word for Mac:

  • Insert a text (default font „Calibri“)
  • Insert an arrow with Windings
  • Insert an arrow with Symbol


The whole text is displayed as Calibri. Even marking the arrows and setting them to Verdana does not change them. This is hilarious. Maybe this is in the source text of the Word doc somewhere. And no idea how OpenOffice handles this.


If I remember correctly TM and (C) do work properly, but this might depend. Oh no:


image


First arrow Windings, the rest Symbol.

image


;-)

image

Just for curiosity: What does your second example look like when there is only one arrow? 



For both arrows:


image


For convenience, it would be easier to have only a tag to insert (but only if the proposal won't be implemented).


Currently: Insert a tag, copy the square, insert a tag.

Then: Insert a tag.


A guess: The editor element on the source side is quite limited (does not display bold, italic etc.), maybe it can only display one font. Perhaps a good idea to switch to another editor element on the long run.

One more guess: This symbol is in addition put bold, so CT might be unable to show it as a tag only.

Login to post a comment