# Gramps 6.0 and gedcom 7

**URL:** <https://gramps.discourse.group/t/gramps-6-0-and-gedcom-7/6950>\
**Category:** Beta Testing\
**Tags:** data-import, gedcom7\
**Created:** [February 7, 2025, 5:14pm UTC](https://gramps.discourse.group/t/gramps-6-0-and-gedcom-7/6950 "2025-02-07T17:14:32Z")\
**Posts on this page:** 1\
**Showing post:** 17

<div class="post-metadata">

**Author:** ![emyoulation](https://yyz2.discourse-cdn.com/free1/user_avatar/gramps.discourse.group/emyoulation/32/67_2.png) [@emyoulation](https://gramps.discourse.group/u/emyoulation)\
**Post date:** [February 8, 2025, 4:28pm UTC](https://gramps.discourse.group/t/gramps-6-0-and-gedcom-7/6950/17 "2025-02-08T16:28:01Z")

</div>

> [@StoltHD](#):
>
> Yeh, but “gedcom 7” doesn’t mean a lot if the file itself is character encoded as ANSI or ANSEL or if the file is encoded correctly with or without the BOM marker or if the BOM marker is at a wrong place or missing…

The GEDCOM7 decision to drop the character encoding and assume UTF-8 seems a bit myopic. Particularly when the existence of [UTF-16](https://wikipedia.org/wiki/UTF-16) and [UTF-32](https://wikipedia.org/wiki/UTF-32) imply that there is current insufficiency. And so UTF-8 is certainly not future‐proof.

The GEDCOM7 .ged reference file that everyone is supposed to test against:  
[https://gedcom.io/testfiles/gedcom70/maximal70.ged](https://gedcom.io/testfiles/gedcom70/maximal70.ged)

---

_[View the full topic](https://gramps.discourse.group/t/gramps-6-0-and-gedcom-7/6950)._