After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 112377 - UML exported to LaTeX issue
UML exported to LaTeX issue
Status: RESOLVED FIXED
Product: dia
Classification: Other
Component: exports
0.91
Other Linux
: Normal normal
: ---
Assigned To: Dia maintainers
Dia maintainers
: 133722 (view as bug list)
Depends on: 124464
Blocks:
 
 
Reported: 2003-05-06 09:56 UTC by ClémentXVII
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description ClémentXVII 2003-05-06 09:56:55 UTC 
When exporting UML into LaTeX documents, there is a 'bug' when exporting a
protected class.

The UML symbol for protected is the # symbol, and this is also a reserved
symbol in LaTeX. The only workaround I found is to find any '#' in the .tex
file, and put a backslash before it so that latex treats it as a normal
character. (ie: '#' is replaced by '\#')
Comment 1 Hans Breuer 2003-07-18 23:25:48 UTC 
It would be useful to know which xport format you used.
PsTricks ? Are there more special characters which need
to be escaped ?
Comment 2 ClémentXVII 2003-07-18 23:32:41 UTC 
I used the normal Dia 'export to LaTeX' feature, with PsTricks.

It seems to me that it is the only character to be escaped... but who
knows, it might not be bad to protect the '%' ande '$' characters...
Comment 3 Hans Breuer 2004-01-11 23:06:58 UTC 
at least it appears so ...
Comment 4 Lars Clausen 2004-02-23 15:02:52 UTC 
*** Bug 133722 has been marked as a duplicate of this bug. ***
Comment 5 Hans Breuer 2004-11-01 08:33:44 UTC 
*** Bug 143414 has been marked as a duplicate of this bug. ***
Comment 6 Hans Breuer 2004-11-06 01:24:04 UTC 
2004-11-01  Hans Breuer  <hans@breuer.org>

        * plug-ins(tex_escape_string) : fixed it [g_utf8_next_char
        will never become NULL but only point to the next char
        which might indeed be \0]
        Use tex_escape_string() to avoid writing invalid tex,
        fixes bug #112377