Search Forums
Forums
Kiwitrees on Twitter
    Tags

    updates, login, privacy, 3.3.0, error, custom, custom modules, feedback, administration pages, permissions, relationships, 1939 Register, HTML block, follow, danish, 3.1, title, check, redirect, source, type, css, ckeditor, sanity, events of close relatives, modules, kiwitrees theme, themes, custom text, 3.0.0. setup, IE11, folder, clippings cart, white screen, release, slideshow, upgrade, Relationship, editor, 3.2.3, icons, ID notes, googlemaps, fact, json, media_links, sanity checker, Google Maps, research tasks, php 7, REFN, partner, 3.2.2, google, message contactform, MYSQL, login failure, marriage, dead, MAC

    Topic:   Name limitations  

    This topic contains 2 replies, has 2 voices, and was last updated by macalter macalter 2 years ago.

    Viewing 3 posts - 1 through 3 (of 3 total)
    • Author
      Posts
    • #4451
      macalter
      macalter
      Participant

      534 posts

      Seem to recall reading that there’s a limit on length of names – GIVN, SURN = NAME. Reason I ask is I’m running into problems with some of my royals who have tons of first names. What seems to happen is 1 NAME will appear correct however 2 GIVN will be the Surname and 2 SURN will either be empty or partial full name; 2 _MARNM will be married surname only.

      Not sure how to overcome with a workaround. I’m leaving Q4050 as one such record. Her name as I want to display it:

      1 NAME Sophie Amelie Adelheid Louise Johanne Leopoldine BRAGANZA
      2 GIVN Sophie Amelie Adelheid Louise Johanne Leopoldine
      2 SURN BRAGANZA
      2 _MARNM Sophie Amelie Adelheid Louise Johanne Leopoldine Löwenstein-Wertheim-Rosenberg

      What I get (due, I think, to wrap around)
      1 NAME Sophie Amelie Adelheid Louise Johanne Leopoldine BRAGANZA
      2 GIVN BRAGANZA
      2 SURN Sophie Amelie Adelheid Louise Johanne Leopoldine Löwenstein-
      2 _MARNM Wertheim-Rosenberg

      Some of the names are even longer than this.

      -----
      Kiwitrees:
      "A-D connections 3.3.0 (rev)"
      PHP 5.6.29 Fast CGI

      "The Royals 3.3.0.."
      PHP 7.0 Fast CGI
      mySQL server: 5.1.56
      MacOS: 10.11.6  (El Capitan)
      Browsers (mac): Safari  Version 10.1.1 (11603.2.5);  Firefox 53.0.2
      [updated: 22 May 2017]

      #4452
      kiwi
      kiwi
      Keymaster

      1431 posts

      There are always limits, but they are far far greater than you are using on that record.

      The GEDCOM spec sets the limit to 120 characters for each “name piece”, i.e. 120 for GIVN, plus 120 for SURN, etc. Your name aboce isn’t even half of that. The database will store far greater sizes than that and does not work strictly to the GEDCOM limit.

      You are more likely to experience display problems than storage. Names are displayed in many places, and they all have some sort of dimensional limitation.

      When I look at your Q4050 record I don’t see any problem, so unless you have changed something since you posted the question, then I don’t see a problem. That then suggests the issue is your screen size / font size / browser zoom setting etc…..

      Attached are shots of the GEDCOM raw edit screen and the INDI header on my machine.

      Nigel

      My personal kiwitrees site is www.our-families.info

      Attachments:
      You must be logged in to view attached files.
      #4455
      macalter
      macalter
      Participant

      534 posts

      Ah, think I figured it out. When I stretched out the screen, the name fits better. In fact, her daughter’s name is even worse!!
      Mac users (that I’ve known) don’t use full/near full screen browser window. When I stretch out the daughter’s name, it’s okay.
      Was puzzled because my raw code was okay — but wider browser wasn’t on the radar.

      -----
      Kiwitrees:
      "A-D connections 3.3.0 (rev)"
      PHP 5.6.29 Fast CGI

      "The Royals 3.3.0.."
      PHP 7.0 Fast CGI
      mySQL server: 5.1.56
      MacOS: 10.11.6  (El Capitan)
      Browsers (mac): Safari  Version 10.1.1 (11603.2.5);  Firefox 53.0.2
      [updated: 22 May 2017]

    Viewing 3 posts - 1 through 3 (of 3 total)

    You must be logged in to reply to this topic.