You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Windows 10 (and I think that also with W8.1), when we type inside a text defined as MS Sans Serif the font associated to the new text written can be automatically modifed to other font (Calibri in my case).
The problem seems to be related to a RTF, probably bad constructed, in wich the tag \fcharsetN associated to the default font is missing.
This problem doesn't occur with tab notes but only with tree notes (with the corresponding nodes), because of a slight difference in the instructions used in the editor initialization (since v1.6.5). That instructions seemed to be unnecessary but also inofensive.
That differences cause in some ocassions that the generated code is not properly managed. Example:
Bad: {\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang3082{\fonttbl{\f0\fnil MS Sans Serif;}} .....
Ok: {\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang3082{\fonttbl{\f0\fnil\fcharset0 MS Sans Serif;}} .....
In Windows XP and in Windows 7 (at least) this is not a problem, because the RichEdit control manage both rtf code correctly.
For new nodes the problem is avoided using a default font different to MS Sans Serif. But for existing nodes with that problem (not occurs in all) the solution is to replace "\f0\fnil " with "\f0\fnil\fcharset0 ".
In Windows 10 (and I think that also with W8.1), when we type inside a text defined as MS Sans Serif the font associated to the new text written can be automatically modifed to other font (Calibri in my case).
The problem seems to be related to a RTF, probably bad constructed, in wich the tag
\fcharsetN
associated to the default font is missing.This problem doesn't occur with tab notes but only with tree notes (with the corresponding nodes), because of a slight difference in the instructions used in the editor initialization (since v1.6.5). That instructions seemed to be unnecessary but also inofensive.
That differences cause in some ocassions that the generated code is not properly managed. Example:
Bad:
{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang3082{\fonttbl{\f0\fnil MS Sans Serif;}} .....
Ok:
{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang3082{\fonttbl{\f0\fnil\fcharset0 MS Sans Serif;}} .....
In Windows XP and in Windows 7 (at least) this is not a problem, because the RichEdit control manage both rtf code correctly.
For new nodes the problem is avoided using a default font different to MS Sans Serif. But for existing nodes with that problem (not occurs in all) the solution is to replace
"\f0\fnil "
with"\f0\fnil\fcharset0 "
.Related info: http://latex2rtf.sourceforge.net/rtfspec_6.html
The text was updated successfully, but these errors were encountered: