Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem with MS Sans Serif in Windows 10 in certain situations #524

Closed
dpradov opened this issue Nov 18, 2015 · 1 comment
Closed

Problem with MS Sans Serif in Windows 10 in certain situations #524

dpradov opened this issue Nov 18, 2015 · 1 comment

Comments

@dpradov
Copy link
Owner

dpradov commented Nov 18, 2015

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

@dpradov dpradov added this to the 1.7.9 milestone Nov 18, 2015
dpradov added a commit that referenced this issue Nov 18, 2015
…in situations

Signed-off-by: Daniel Prado Velasco <dpradov@users.noreply.github.com>
@dpradov
Copy link
Owner Author

dpradov commented Nov 18, 2015

I will also add a command line option to KeyNote to fix the problem in existing nodes, making the replacement indicated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant