Thank you very much! We'll get back to this next week after winter vacation.

Okay, thank you again, this is an excellent PR description. After reading the PR, I agree with all your changes except maybe one:

“庄司” is the kanji representation of a Japanese surname "Shoji" and is not a full name. According to Japanese law, a full name must include both a family name and a given name. The only exception to this rule applies to members of the Imperial Family.
Therefore, I suggest revising the example to “明仁” (Akihito, Emperor Emeritus of Japan).

Since most users of the system will not be members of the Imperial Family – wouldn't it be clearer to change the example to a common full name that includes both family name and given name?

It should also be noted that in some regions of Asia, legal names consist only of given names without surnames. If pretix plans to support languages from such regions in the future, it would be more appropriate to use examples of full names from those languages in this section. (e.g., Burmese, traditional Mongolian, Javanese, etc.)

I think our goal should be to provide enough "name formats" such that they are usable for every region where someone wants to use pretix. I think our goal should not necessarily be to have the examples work everywhere. For some of the name formats we solve this by the examples themselves being part of the gettext translation but this feels weird for the ones where there is no English "source expression".

Thank you as always. Your concerns are very well-founded.
I've revised the file.

The example of a name without a family name has been changed to ‘Aye,’ a very common name in Myanmar. This name is gender-neutral and is comparable to ‘John’ or ‘Mary’ in English as a typical first name. It should also be noted that Burmese people do not have family names. (In Burmese transcript, this name is written as 'အေး'. It looks just like '632:'!)

However, I am unsure if this change will be acceptable to everyone. This is because, living in Asia, I can easily understand the existence of such names, but for those in Europe, it might seem like an unusual name.

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.27%. Comparing base (f1bdd3b) to head (00b5f10).
Report is 64 commits behind head on master.

@@            Coverage Diff             @@
##           master    #4727      +/-   ##
==========================================
- Coverage   78.27%   78.27%   -0.01%     
==========================================
  Files         443      443              
  Lines       62706    62713       +7     
==========================================
+ Hits        49082    49087       +5     
- Misses      13624    13626       +2     

Thank you as always. Your concerns are very well-founded.
I've revised the file.

Ah, sorry, I think we still have a misunderstanding. I think this makes it worse? Now both fields of the example contain the same name. That makes it hard to use the example to help understanding how the name works.

I hope it's okay if I use your name as an example at hand, I only use it because it's on your website so I assume your full name is not private information (happy to delete the comment otherwise).

The intention of this name format was:

• full_name: 梅本聖 (hopefully that's the right order for a "full name"?)
• latin_transcription: Hijiri Umemoto

To paraphrase: The idea was to allow users to enter both their native spelling of the name (in whatever language or name format they like!) as well as a latin-character-set friendly version of the name (in whatever order they like). One purpose of this at e.g. an international scientific conference would be to print both on the name tag of a person, so they have their name in its original form on their name tag (which is a respectful thing to allow them to have) as well as a version that allows people from other countries to read or search that name.

Now, obviously, neither the "Aye" example nor the "Akihito" example is wrong, but I think they fall short at illustrating the concept. "Aye", because no difference between the fields is necessary, "Akihito" because it uses an edge-case of the definition of "full name" which might confuse people who are aware of the differences in Japan.

The fact that we have these misunderstandings might mean that the idea behind this name format is flawed or not as useful as we thought it was – in which case we'd be happy to add more formats, but at least for backwards compatibility I'd like to keep it and improve on the example / description.

Thank you for your detailed explanation regarding the intention and purpose behind the name format. I now have a much clearer understanding that this system is designed to support both “native script” and “Latin script” name representations, enhancing usability in international contexts.

As for using my name as an example, I have no objections since it is already publicly available on the website. In fact, I’d be glad if it helps clarify the concept in a meaningful way!

Ah, I was using your name as an example for the purposes of this comment here, I would also be fine with it making it into the codebase but if you have a suggestion for a good generic example, that would also be fine. Your name was just the one I was most confident making a "correct" example here, seeing that I speak no Japanese at all. (I had two years of Mandarin in school, which means I can tell the difference between Kanji from Kana but that is absolutely where my knowledge ends :D)

Are there some name combinations in Japan that is so common that it's a good example, like there are tens of thousands of "James Smith" in the US?

In Japan, we have names like ‘Yamada Taro’ (male) and ‘Yamada Hanako’ (female), which function similarly to ‘John Doe’ in English. While there aren’t many real people with those names, everyone understands them as sample names.

Perfect!