Jump to: navigation, search

Known issues

296 bytes added, 22 January
See also
{{languagesstub}}This page lists Lists of some long-standing recurring issues with Gramps. Be sure also to read the instructions on [[using the bug tracker]], and to check the bug tracker to learn what the current actively researched issues are --- they aren't reported here.
===Gramps and some Gtk versions===
* Some Gtk versions seem not to properly refresh the GUI (need to use the mouse cursor), see bug {{bug|4863}} CLOSEDOnly an issue for Gramps 3.x / Not reproducible in Gramps 4.x or newer.
* Some Gtk versions have a refresh issue on Citation TreeView (3.4.x) after an edition, see bug {{bug|5688}} FEEDBACK.
* Incremental search and synchronization with typed letters, see bug {{bug|1450}}Resolved in Gramps 4.2.0.* New row/line on [[Census_Addons|Census gramplet (addon)]], see bug [ 5688] Only an issue for Gramps 3.x / Not reproducible in Gramps 4.x or newer..
* Layout issue for menu into Geography, see bug [ 5742].
* Gramps freezes after editing a data, see bug {{bug|7772}}. Fixed by using GTK+ 3.14.8 or higher.
===Gramps and some python gobject introspection versions===
If Python returns a codec/UTF8 warning and this file was pasted from an external support (CD, HD, USB key), maybe filename has been corrupted ! It seems correct on screen but not on command line. Your OS was not able to properly set the encoding used on your external support.
The [ replacement character ] will be often a "�" (black diamond with a white question mark)]
You can try to fix the filename by setting the correct character. Now you will be able to import this file into Gramps !
* (resolved) {{bug|6883}} non-Western fonts broken in PS reports
* (resolved) {{bug|6884}} RTF reports backend seems to be non-UTF-aware, breaks non-Western text
=See also=
* [[Known issues]]
* [[Common problems]]
* [[Font troubleshooting]]
* [[Gramps and Windows]]
[[Category:Developers/Quality Assurance]]

Navigation menu