This article helps you create a shortlist of domain name candidates by combining pinyin initials with English roots. You will define your project's core keywords, generate variations, and check basic character constraints without needing technical setup knowledge.
Defining Your Project Keywords
This is a hypothetical scenario. An independent developer is preparing a small personal reading-log project and wants a shortlist of name candidates built from pinyin initials plus familiar English roots. Before inventing anything, she opens a plain text file and defines her project keywords in a small worksheet she calls “reading-list starter.”
Her worksheet has four columns: Core Chinese words, Their pinyin, The initials she will use, and English roots that fit. Two fictional entries show how it works. In the first row she writes “读书” as the core word, notes the pinyin “du shu,” records the initials “d” and “s,” and lists the root “log.” In the second row she writes “每天” for “every day,” notes “mei tian,” keeps “m” and “t,” and lists “note.” These are examples she invented to explain the method to herself, not records of a real service or audience research.
She then writes three candidate names by joining the letters in different orders. The first is “dslog,” which puts the reading-related initials first and the root last. The second is “mtnote,” using the daily-reading initials and the writing root. The third is “dailystudy,” which drops initial joining entirely and lets the English root carry the meaning. She adds a one-line reason beside each: “dslog” reads compactly, “mtnote” is easy to say once the initials are explained, and “dailystudy” is the clearest but longest of the three.
For a quick comparison, she picks one example trade-off. She prefers “mtnote” over “dailystudy” because the shorter form leaves more room for a two-word title on a project page, while she keeps “dailystudy” as a fallback if she later wants a name that needs no explanation. She does not treat any candidate as accepted by a registrar or a username field; those checks come later.
At the bottom of the file she leaves three blank lines labeled “shortlist,” “reason to drop,” and “next check,” so the keyword worksheet feeds directly into the next naming step rather than becoming a list of vague preferences.
Combining Pinyin Abbreviations with Roots
You can take your keyword worksheet and turn it into a naming shortlist by pairing each pinyin initial with two or three familiar roots, then choosing which pairings read cleanly enough to keep. For a hypothetical reading-log project, the worksheet might list 读书 (dushu) and 日志 (rizhi), note the initials ds and rz, and set beside them roots such as log, note, daily, and page. From that row you might try dslog, rzlog, dsnote, and rzpage, then decide which ones you would actually say aloud to a friend. The point is not to invent ten names at once; it is to let one row produce a handful of candidates and cross out the ones that feel clumsy.
A simple habit is to compare the short form against a longer phrase before you commit. Suppose you prefer “mtnote” to “mydailytable” because the shorter version still hints at the project and leaves room for a two-word title above the name. You can write both on separate lines, add one phrase explaining why the shorter one fits, and mark the longer one as “dropped: too long to type.” That sentence is your own judgment, not a rule, so keep it brief and honest.
You might also keep root choices narrow: one root for the action, one for the record. If “log” already says what the project does, pairing it with a second verb root like “track” gives you “dstracklog,” which is harder to read. Consider allowing one root only in the final candidate, then letting the pinyin initials carry the meaning. When you finish a round, you can leave three empty lines at the bottom of the file labeled “shortlist,” “reason dropped,” and “next root to try,” so the next session starts from a concrete place rather than a blank page.
Checking Character Restrictions
UTS #39 describes a General Security Profile for identifiers that restricts characters not in common use, characters used only in specialized fields, and characters in limited use by very small communities. The profile treats characters with Identifier_Status=Restricted as disallowed unless an implementation documents the additional characters it allows.1
To test a candidate identifier, the specification applies canonical equivalence: a sequence such as u followed by a combining diaeresis is Allowed if either u and the diaeresis are Allowed, or the precomposed ü is Allowed.1
You can keep the shortlist usable by adding a character-count check to each candidate before deciding. Take “mtnote” and “dslog”: jot the letter count beside each, then note whether the count comes from initials, roots, or both. A name that is short only because a root was dropped may read as an abbreviation you have to explain every time.
It also helps to compare how each candidate sounds when spoken once. You might write “mtnote — say it aloud” beside one row and “dslog — spell it to a friend” beside another, then mark which one you would rather repeat. These are notes for your own comparison, not a test result.
For the worksheet, consider adding two fields: “short form” and “long form.” For the reading-log example, “mtnote” could sit under short form and “mydailytable” under long form, with a reason noting that the shorter one leaves room for a title. For an archived entry, the same fields can hold an older candidate and its reason for being set aside.
Organizing Candidate Shortlists
You can turn the loose candidates from your worksheet into a shortlist you can actually decide between by giving each row a small, fixed set of fields. Consider marking every candidate as either current or archived, and then filling the same three columns for both kinds of entry: “intended project use,” “sounds-like or spelling risk,” and “next action.” For a personal reading-log project, a current row might read “mtnote — current — used as the short working name; risk: readers may type ‘mt’ as two letters; next action: keep on shortlist.” An archived row could read “dailystudy — archived — kept only as a comparison label; risk: sounds like a formal service; next action: leave out of the final choice.” The fields stay the same, and only the status column changes.
You might also add one comparison step before you narrow the list. Pick two candidates that share a root but differ in initial order, then write a single sentence for each explaining why you would keep or drop it. “I prefer dslog because the reading initials come first and the root ‘log’ makes the purpose obvious” is more useful than a bare preference, because it gives you a reason you can revisit later. This is a hypothetical exercise with your own names, not a test of whether a name is available or how it will perform.
Consider grouping the shortlist into two small blocks: names you would keep as written, and names you would change if a longer form felt clearer. Keep one plausible long form beside each short one so the choice is visible, such as “mtnote — alternative: mytable note.” You can also mark which candidates you would check first if you later decide to look into registration, leaving that as a planned next step rather than a completed check. When the list grows past a handful of rows, you might sort by the “next action” column so the names you intend to keep and compare sit together, while the rest stay as archived reference.
Selecting Final Options
With your rough candidates in hand, you can move from gathering to deciding by giving each row a compact set of fields and filling them in yourself. Consider labels like candidate, short form, long form, spoken test, and reason kept or dropped. In the reading-log example, a filled row might read: candidate “mtnote,” short form “mtnote,” long form “mydailytable,” spoken test “say it once, then spell it,” reason kept “short and keeps the record idea.” A second row could read: candidate “dslog,” short form “dslog,” long form “dailystudy log,” spoken test “spell it to a friend,” reason dropped “two meanings compete.” Filling each row this way turns a loose list into something you can compare side by side.
You might then add a single comparison sentence to each candidate rather than a long justification. For “mtnote,” that sentence could be: “It keeps the table and note ideas without spelling out either in full.” For “dslog,” it could be: “It carries the reading initials but the log root already says the job.” One sentence per row keeps the file scannable and forces you to name the one thing that matters most about each option.
Consider splitting the shortlist into two blocks: names you would keep exactly as written and names you would adjust if a longer form read more clearly. Move “mtnote” into the first block and place “dslog” in the second with a note like “try dsnotes or dsrecord.” Leaving both blocks open means you are not discarding a direction too early, only marking which ones still need a wording change before you settle.
Next Steps for Registration
You can take your filled worksheet and move one step closer to registration by marking, for each candidate, what you would still need to decide before acting. Consider a compact row of fields you complete yourself: candidate name, preferred spelling, intended suffix, backup spelling, and the single reason you would keep it. Filling this in for “mtnote” might read: candidate “mtnote,” preferred spelling “mt-note” if a separator helps readability, suffix left open, backup “mtnotebook,” reason “short and ties to the table-and-log idea.” For “dslog” you might write backup “dslogbook” and the reason “starts with the reading initials.”
Keep the fields provisional on purpose. You can add a “hold or drop” marker and a one-line note about why, rather than treating the row as final. If “dslog” reads quickly but feels close to another word you know, note that as a question to settle later rather than a verdict. The point is to leave yourself a clear record of your own reasoning, so a later choice does not depend on memory.
You might also compare two rows side by side before deciding which one to advance. For example, put “mtnote” and “dslogbook” next to each other and write which one you would rather type repeatedly and which one you would rather say aloud to a friend. If the shorter form wins on typing but the longer form wins on clarity, you can choose which priority matters more for your project and record that choice in the reason column.
Before narrowing to one name, consider which fields you can answer confidently and which remain open questions for you. You can mark open items plainly, such as an undecided suffix or a spelling you are still weighing, and leave them visible rather than filling them in prematurely. That way your shortlist stays honest about what you have actually settled.
Frequently asked questions
How can I turn my keyword worksheet into a naming shortlist?
You can take your keyword worksheet and turn it into a naming shortlist by pairing each pinyin initial with two or three familiar roots, then choosing which pairings read cleanly enough to keep. For a hypothetical reading-log project, the worksheet might list 读书 (dushu) and 日志 (rizhi), note the initials ds and rz, and set beside them roots such as log, note, daily, and page.
What fields can I use to turn loose worksheet candidates into a shortlist I can decide between?
You can turn the loose candidates from your worksheet into a shortlist you can actually decide between by giving each row a small, fixed set of fields. Consider marking every candidate as either current or archived, and then filling the same three columns for both kinds of entry: “intended project use,” “sounds-like or spelling risk,” and “next action.”
What small set of fields can I fill in myself to move my rough candidates from gathering to deciding?
With your rough candidates in hand, you can move from gathering to deciding by giving each row a compact set of fields and filling them in yourself. Consider labels like candidate, short form, long form, spoken test, and reason kept or dropped.
UTS #39: Unicode Security Mechanisms . Retrieved 2026-11-19. ↩︎ ↩︎