Home› Welcome to the FamilySearch Community!› Suggest an Idea

URL-encoding (percent encoding) appears in the comments when attaching records.

Alice_Allen
Alice_Allen
February 8, 2021 edited October 21, 2021 in Suggest an Idea

This is a recent issue. It happens consistently. I am using the Chrome browser and it is up-to-date.


Example, M5HX-TQY.


I attached a census record to members of this family and included (in the "Reason This Source Is Attached" section) the comment, "1880 US Census. George CRANCE, wife Anna, and one child at Van Etten, Chemung Co, NY."


When viewing in Sources, the comment appears, "1880%20US%20Census.%20George%20CRANCE%2C%20wife%20Anna%2C%20and%20one%20child%20at%20Van%20Etten%2C%20Chemung%20Co%2C%20NY."


The encoding makes the comment difficult to read. How do I eliminate this behavior so I can include useable content in the "Reason" section?


Thank you, in advance, for your assistance.


Notes:

1) Issue is not limited to US census records. Same result when attaching US pension record.

2) I had posted this issue to "Questions" and was directed to post to "Ideas."

0
0
0 votes

New · Last Updated October 21, 2021

Comments

  • Brett .
    Brett . ✭✭✭✭✭
    February 8, 2021

    FamilySearch

    .

    FYI

    .

    As "Reported", TWICE, that I know of, in the "Community.FamilySearch" Forum ...

    .

    'Group' being "General Questions" ...

    .

    ------------------

    .

    By THIS poster ...

    .

    9 February 2021 ( Early this morning, 8 Hours ago)

    .

    URL-encoding (percent encoding) appears in the comments when attaching records.

    This is a recent issue. It happens consistently. I am using the Chrome browser and it is up-to-date.

    Example, M5HX-TQY.

    I attached a census record to members of this family and included (in the "Reason This Source Is Attached" section) the comment, "1880 US Census. George CRANCE, wife Anna, and one child at Van Etten, Chemung Co, NY."

    When viewing in Sources, the comment appears, "1880%20US%20Census.%20George%20CRANCE%2C%20wife%20Anna%2C%20and%20one%20child%20at%20Van%20Etten%2C%20Chemung%20Co%2C%20NY."

    The encoding makes the comment difficult to read. How do I eliminate this behavior so I can include useable content in the "Reason" section?

    Thank you, in advance, for your assistance.

    .

    https://community.familysearch.org/s/question/0D54V00005BRQT7SAP/urlencoding-percent-encoding-appears-in-the-comments-when-attaching-records

    .

    ------------------

    .

    By ANOTHER poster

    .

    4 February 2021

    .

    Language Erosion Attaching Sources 2-3 February 2021???

    Is anyone else having difficulty with language attaching sources yesterday and today? For example, I type "United States Census, 1910, Household of Jacob L Davis (Head)," and the program changes it to "United%20States%20Census%2C%201910%0AHousehold%20of%20Jacob%20L%20Davis%20(Head)."

    https://community.familysearch.org/s/question/0D54V00005BPRvySAH/language-erosion-attaching-sources-23-february-2021

    .

    ------------------

    .

    I suggested they BOTH post in, BOTH,

    (1) THIS Forum; and,

    (2) ALSO submit 'FamilySearch' "Support" Cases

    .

    Submitted for your IMMEDIATE, information; attention; and, consideration.

    .

    Brett

    .

    0
  • Brett .
    Brett . ✭✭✭✭✭
    February 8, 2021

    FamilySearch

    .

    FYI

    .

    As "Reported", TWICE, that I know of, in the "Community.FamilySearch" Forum ...

    .

    'Group' being "General Questions" ...

    .

    ------------------

    .

    By THIS poster ...

    .

    9 February 2021 ( Early this morning, 8 Hours ago)

    .

    URL-encoding (percent encoding) appears in the comments when attaching records.

    This is a recent issue. It happens consistently. I am using the Chrome browser and it is up-to-date.

    Example, M5HX-TQY.

    I attached a census record to members of this family and included (in the "Reason This Source Is Attached" section) the comment, "1880 US Census. George CRANCE, wife Anna, and one child at Van Etten, Chemung Co, NY."

    When viewing in Sources, the comment appears, "1880%20US%20Census.%20George%20CRANCE%2C%20wife%20Anna%2C%20and%20one%20child%20at%20Van%20Etten%2C%20Chemung%20Co%2C%20NY."

    The encoding makes the comment difficult to read. How do I eliminate this behavior so I can include useable content in the "Reason" section?

    Thank you, in advance, for your assistance.

    .

    https://community.familysearch.org/s/question/0D54V00005BRQT7SAP/urlencoding-percent-encoding-appears-in-the-comments-when-attaching-records

    .

    ------------------

    .

    By ANOTHER poster

    .

    4 February 2021

    .

    Language Erosion Attaching Sources 2-3 February 2021???

    Is anyone else having difficulty with language attaching sources yesterday and today? For example, I type "United States Census, 1910, Household of Jacob L Davis (Head)," and the program changes it to "United%20States%20Census%2C%201910%0AHousehold%20of%20Jacob%20L%20Davis%20(Head)."

    https://community.familysearch.org/s/question/0D54V00005BPRvySAH/language-erosion-attaching-sources-23-february-2021

    .

    ------------------

    .

    I suggested they BOTH post in, BOTH,

    (1) THIS Forum; and,

    (2) ALSO submit 'FamilySearch' "Support" Cases

    .

    Submitted for your IMMEDIATE, information; attention; and, consideration.

    .

    Brett

    .

    0
Clear
No Groups Found

Categories

  • 22.8K All Categories
  • 379 1950 US Census
  • 46K FamilySearch Help
  • 89 Get Involved
  • 2.3K General Questions
  • 329 Family History Centers
  • 326 FamilySearch Account
  • 3.2K Family Tree
  • 2.5K Search
  • 3.6K Indexing
  • 435 Memories
  • 4.3K Temple
  • 251 Other Languages
  • 29 Community News
  • 5.3K Suggest an Idea
  • Groups