Non-English songs for Musixmatch
Each convention keeps its source, language scope and the part that still needs judgment.
The checks below catch specific patterns in your text. They support your review; passing them does not verify every part of a convention.
Generally use original scripts
Generally use original scripts; consult the linked romanization guidance for details.
What LyricLint can establish
Retain original script; no automatic transliteration. See official supplemental sources below.
The described translation feature is desktop-only
What LyricLint can establish
Native workflow limitation; local preservation is a separate capability.
Translate the existing formatted lines individually
Translate the existing formatted lines individually; do not combine several source lines into one translation line.
What LyricLint can establish
Preserve known alignment metadata; no automatic translation. Japanese has a meaning-distribution qualification.
Prefer verified, locked source lyrics to reduce later translation loss
What LyricLint can establish
Recommendation, not a text-validation error or a claim LyricLint can verify the lock.
Transcription and formatting rules also apply to translations
What LyricLint can establish
Track translation status explicitly; do not infer it from script/header vocabulary.
Preserve the source line's tone
What LyricLint can establish
Human linguistic review.
Retain words/names that cannot sensibly be translated
What LyricLint can establish
No automatic proper-name translation or normalization.
Convey the intended message idiomatically instead of mechanically translating each word
What LyricLint can establish
Outside deterministic format conversion.
Seek help/research instead of leaving blanks or question-mark replacement tokens for undeciphered words
What LyricLint can establish
Direct conflict with Genius [?] for English. Keep the uncertainty visible as unresolved work; neither delete the token nor invent a word.
Checks for this convention
A word still needing transcription
Requires review under this check We hear [?] tonight
The English Musixmatch FAQ rejects question-mark replacement tokens. Keep this uncertainty visible until listening or research establishes the word; deleting the token or inventing lyrics would lose information.
Accepted by this check We hear rain tonight
A word still needing transcription , with trigger and fix details
Ask for confirmation of unlisted abbreviated forms
What LyricLint can establish
A deterministic engine can report missing coverage, not invent an approved spelling or contact a contributor.
Secondary vocals use parentheses and generally lowercase beginnings unless grammar or sentence-ending punctuation calls for capitals
What LyricLint can establish
Ordinary vocalizations and grammatical openings such as Whatever lowercase within a lead line when converting Genius wording, and offer a preview correction for native Musixmatch wording. Names, English I, sentence punctuation and uncertain vocal roles retain contextual review.
Checks for this convention
Capitalized backing vocals
Flagged example We return (Yeah)
Ordinary English backing-vocal openings use lowercase inside a lyric line. Pronouns, names and new sentences keep their grammatical capitals.
Accepted by this check We return (yeah)
Fix: Lowercase “Yeah”
Capitalized backing vocals , with trigger and fix details
Align the first sound without a lead-in
Align the first sound without a lead-in; include live speech and remix vocals unless effects make them genuinely indecipherable; listen to the entire track before marking it instrumental.
What LyricLint can establish
Authoritative workflow qualification, not proof that current anchors are accurate or that a long opening means an instrumental track.
Supplies brand spellings and context-dependent short names
What LyricLint can establish
Curated identity evidence; do not expand every nickname or treat brand recognition as certain.
Supplies British, Nigerian, Patois and contemporary slang with meanings and allowed variants
What LyricLint can establish
These are separate lexical inventories; translating dialect into standard English is not a correction. A token's meaning still matters.
Preserve the dialect actually sung instead of standardizing an original transcription to Bokmål/Nynorsk
What LyricLint can establish
Existing Genius-mode dictionary checks are narrow language curation; never use them to erase sung Norwegian dialect in MXM. Artist origin is suggested human research, not an automatic dialect classifier.
Use normal Norwegian proper-name/acronym case and the company's/product's actual casing
What LyricLint can establish
Does not expressly revoke the main line-initial rule. Preserve names such as mixed-case brands; do not blanket-case tokens.
Prefer Bokmål for translations into Norwegian
Prefer Bokmål for translations into Norwegian; compound translations normally join, with hyphens for certain long/readability cases.
What LyricLint can establish
The Bokmål preference is translation-specific, not authorization to normalize original dialect lyrics. Compound analysis needs language context.
Sámi is a separate language whose writing must be retained
Sámi is a separate language whose writing must be retained; knowledgeable transcription is needed. Lyricless joik is described as instrumental.
Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.
What LyricLint can establish
Do not map Sámi into Norwegian or remove vocables by heuristic. The joik reference to #INSTRUMENTAL needs reconciliation with the main interior-only marker rule and track-level instrumental workflow.
English nouns embedded in German use noun capitals
English nouns embedded in German use noun capitals; English clauses retain English grammar; borrowed verbs/adjectives remain lowercase; specified adjective+noun combinations capitalize both.
What LyricLint can establish
Token-level “English-looking word” detection cannot choose the rule. Existing Genius title-case diagnostics are not a German grammar engine.
A curated elision table depends on actual sung pronunciation and explicitly allows alternatives in several entries, including apostrophized/non-apostrophized forms
What LyricLint can establish
Encode allowed sets and scope, not a single canonical rewrite. Absence from a supplemental table cannot prohibit an official allowed form.
Audible producer tags are lyrics
Audible producer tags are lyrics; a recognition list is supplied.
What LyricLint can establish
Broad agreement on preserving vocals. A list of known tags never authorizes insertion of an unheard tag.
Dialect-shortened words can be independent words without elision apostrophes
Dialect-shortened words can be independent words without elision apostrophes; contractions of separate words use apostrophes.
What LyricLint can establish
Do not “repair” every shortened German dialect token as omitted Standard German letters.
Terminal punctuation is limited to necessary question/exclamation marks and closing parentheses/quotes. Hyphens mark incomplete words
Terminal punctuation is limited to necessary question/exclamation marks and closing parentheses/quotes. Hyphens mark incomplete words; ellipses mark incomplete sentences, not ordinary performance pauses.
What LyricLint can establish
Review interruption/phrase context; do not strip closing syntax or infer ellipses from pauses.
Checks for this convention
Terminal punctuation needing review
Flagged example We return.
Musixmatch excludes commas and non-acronym periods at lyric line endings. Acronyms retain their own punctuation; review names and abbreviations before removal.
Accepted by this check We return
Fix: Remove the period
Terminal punctuation needing review , with trigger and fix details
An unconfirmed interruption
Requires review under this check If we could—
Musixmatch uses a hyphen for an unfinished word and an ellipsis for an unfinished sentence or fade-out. A musical pause alone does not establish either; a Genius dropped-word dash cannot be rewritten from shape alone.
Accepted by this check If we could return
An unconfirmed interruption , with trigger and fix details
A shortened single word generally omits the apostrophe unless it distinguishes another real word
A shortened single word generally omits the apostrophe unless it distinguishes another real word; merged-word contractions use an apostrophe; established colloquial abbreviations can be exceptions.
What LyricLint can establish
Genius's general omission-apostrophe guidance cannot be applied as an unconditional Spanish MXM rule.
Normal accents remain
Normal accents remain; an apostrophe does not replace an accent. Retain original s/z if aspiration/substitution is audible, omitting only when entirely absent.
What LyricLint can establish
Accent checks can be scoped; phonetic presence requires listening.
Actual direct speech uses colon + space + opening quote + capital. Omit the colon if it would end a line. Quotation may span lines. Indirect speech has no colon/quotes
Actual direct speech uses colon + space + opening quote + capital. Omit the colon if it would end a line. Quotation may span lines. Indirect speech has no colon/quotes; hypothetical quoted words keep quotes but receive no colon or automatic initial capital.
What LyricLint can establish
Explicit conflict with MX-F13's comma. Review and encode the Spanish exception; do not apply a global quote-prefix transform.
Checks for this convention
A quotation with unconfirmed meaning
Requires review under this check Dije, "Vuelve"
Spanish direct speech uses a colon, a space and an opening quotation mark, except when the colon would end a line. Indirect speech and hypothetical words differ; quoted artist, song or album names are not necessarily speech.
Accepted by this check Dije que vuelve
A quotation with unconfirmed meaning , with trigger and fix details
Lead normally opens the line and determines sync
Lead normally opens the line and determines sync; sequential secondary lyrics are plain, overlapping/background lyrics parenthesized. Unison/harmony is written once; echoes/reverb/nonhuman effects are excluded. In live performances, a lead's audience-directed aside takes parentheses unless alone on its line. Audience vocals are plain when carrying lyrics or standing alone, otherwise follow background treatment.
What LyricLint can establish
Role/overlap/effect classification needs audio or supplied facts. Performer identity alone does not decide role; text similarity does not prove an echo or simultaneous unison.
Put secondary text midline only where a lead pause accommodates it, otherwise favor line end. Avoid initial parentheses
Put secondary text midline only where a lead pause accommodates it, otherwise favor line end. Avoid initial parentheses; remove them when they enclose an entire line. No punctuation immediately before an opening parenthesis.
What LyricLint can establish
Structural edits can change timing and vocal attachment; require role/placement evidence. No unconditional “move all parentheses” conversion.
Checks for this convention
Spanish backing-vocal placement
Requires review under this check (Vuelve aquí)
Spanish guidance avoids initial or whole-line backing parentheses and punctuation immediately before them. Confirm lead, background, audience and overlapping roles before moving or unwrapping text; the change can affect timing.
Accepted by this check Vuelve (aquí)
Spanish backing-vocal placement , with trigger and fix details
Normally lowercase openings, with grammatical/name and sentence-ending-punctuation exceptions
What LyricLint can establish
Confirmed conflict with Genius's capital-initial ad-lib convention; grammar remains a precondition.
Checks for this convention
Capitalized backing vocals
Flagged example We return (Yeah)
Ordinary English backing-vocal openings use lowercase inside a lyric line. Pronouns, names and new sentences keep their grammatical capitals.
Accepted by this check We return (yeah)
Fix: Lowercase “Yeah”
Capitalized backing vocals , with trigger and fix details
Acronyms use uppercase without separating dots/spaces
Acronyms use uppercase without separating dots/spaces; laughter units use commas.
What LyricLint can establish
Do not infer acronym or laughter role from arbitrary letters.
Checks for this convention
A possible Spanish acronym
Requires review under this check Canto U.S.A.
The Spanish FAQ writes acronyms in capitals without separating dots or spaces. Sung individual letters, abbreviations and names are different cases; their role cannot be inferred from punctuation alone.
Accepted by this check Canto USA
A possible Spanish acronym , with trigger and fix details
Context can justify words above ten
Context can justify words above ten; the source illustrates a large quantity without a complete exception predicate.
What LyricLint can establish
The generic >10 conversion is not unconditional. Review fixed/contextual expressions and large values.
Checks for this convention
A number without established context
Requires review under this check Twenty-one stars
Musixmatch generally spells quantities through ten and uses digits above ten, with separate rules for dates, phones, decades, names, fixed expressions and times. Exact times and o’clock differ. A value alone does not prove its role or pronunciation; no numeric rewrite is offered.
Accepted by this check At dawn
A number without established context , with trigger and fix details
Preserve artist/band spelling/case
Preserve artist/band spelling/case; detailed grammar distinguishes names, religion, geography, celestial objects, titles, dates and ordinary nouns. Mentioned artist, song and album names may be quoted.
What LyricLint can establish
No generic proper-name normalization. Direct speech is not the only permitted quotation role. The current Genius Spanish dictionary rules cover only a small subset.
Contains contextual homophone distinctions and explicit accent conventions, including unaccented solo and specified demonstratives/short verb forms
What LyricLint can establish
Record source-specific lexical cases; not a general accent-removal operation. Meaning-dependent pairs remain review.
Checks for this convention
A source-specific Spanish accent
Flagged example Sólo canto aquí
The Musixmatch Spanish FAQ uses these specified words without a written accent. Check quoted names or embedded-language text before changing the form; this is not a general accent-removal rule.
Accepted by this check Solo canto aquí
Fix: Use Solo
A source-specific Spanish accent , with trigger and fix details
At most 70 characters per lyric line and ten lines per stanza
What LyricLint can establish
Adds a limit missing from the main plan. Unicode counting unit and stanza/tag relationship are unspecified; review the count definition before enforcement and never auto-split at character 70.
Checks for this convention
A long Spanish lyric line
Requires review under this check Volvemos al camino donde cantan los recuerdos y nos esperan las voces del viento
The Spanish FAQ limits lines to 70 characters but does not define the Unicode counting unit. This line has 80 UTF-16 units and 80 Unicode code points. Review musical phrasing and the count; do not split automatically at an arbitrary position.
Accepted by this check Volvemos al camino Donde nos esperan las voces del viento
A long Spanish lyric line , with trigger and fix details
More than ten lines in a lyric block
Flagged example Here we sing Here we stand Here we turn Here we rest Here we dream Here we wait Here we dance Here we stay Here we walk Here we rise Here we return
Musixmatch limits formatted sections to ten physical lyric lines. Choose a break that follows the music and meaning; soft wraps are not extra lines, and a layout break does not establish a new musical tag.
Accepted by this check Here we sing Here we stand Here we turn
More than ten lines in a lyric block , with trigger and fix details
Commas follow grammatical lists/appositions/vocatives, not every audible pause
Commas follow grammatical lists/appositions/vocatives, not every audible pause; coordination has specific exceptions.
What LyricLint can establish
Grammar/audio timing are different inputs; no pause-based comma insertion.
Exclamation marks, colons and semicolons are prohibited, with an exception for punctuation belonging to a sung song title
What LyricLint can establish
Conflicts with general MXM allowance and Genius's excitement-based exclamation convention. Scope the reviewed French rule and name exception explicitly.
Checks for this convention
Restricted French punctuation
Requires review under this check Reviens!
French Musixmatch guidance excludes exclamation marks, colons and semicolons, except punctuation that belongs to a sung song title. Preserve title punctuation; a text-only check cannot establish that exception.
Accepted by this check Reviens
Restricted French punctuation , with trigger and fix details
Required question marks have no preceding space, for grammatical questions or clearly questioning delivery
What LyricLint can establish
Specific typography rule, not a blanket import of ordinary French publishing spacing. Delivery still needs judgment.
Checks for this convention
A space before a French question mark
Flagged example Tu reviens ?
The French Musixmatch article specifically places a question mark without a preceding space. This lyric convention differs from some ordinary French publishing typography.
Accepted by this check Tu reviens?
Fix: Remove the space
A space before a French question mark , with trigger and fix details
Mark beginning/end elisions with apostrophes
Mark beginning/end elisions with apostrophes; retain standard spelling for internal elisions.
What LyricLint can establish
Do not share an unconstrained Genius/English apostrophe inserter.
Join imperatives and pronouns with hyphens
Join imperatives and pronouns with hyphens; verlan retains underlying spelling and hyphenates rearranged syllables.
What LyricLint can establish
Needs grammatical/lexical interpretation; no arbitrary syllable splitting.
The prose spells sub-ten or “precise” times, but its examples also use numeric times with minutes. Exactly ten is not specified
Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.
What LyricLint can establish
Internally ambiguous source: retain wording and block automatic boundary decisions until clarified.
Checks for this convention
A number without established context
Requires review under this check Twenty-one stars
Musixmatch generally spells quantities through ten and uses digits above ten, with separate rules for dates, phones, decades, names, fixed expressions and times. Exact times and o’clock differ. A value alone does not prove its role or pronunciation; no numeric rewrite is offered.
Accepted by this check At dawn
A number without established context , with trigger and fix details
y a has no apostrophe
y a has no apostrophe; French decade expressions and embedded English decade expressions have different constructions.
What LyricLint can establish
Explicit language scope, including mixed-language spans; no global decade-apostrophe rewrite.
Checks for this convention
An apostrophe in the French y a form
Flagged example Y'a du vent
The French Musixmatch FAQ writes this spoken form as y a, without an apostrophe. Preserve unrelated quoted names or embedded languages.
Accepted by this check Y a du vent
Fix: Use y a
An apostrophe in the French y a form , with trigger and fix details
Above-ten quantities normally use digits, but fixed expressions stay in words
What LyricLint can establish
Numeric interpretation must exclude fixed expressions; no blanket >10 conversion.
Checks for this convention
A number without established context
Requires review under this check Twenty-one stars
Musixmatch generally spells quantities through ten and uses digits above ten, with separate rules for dates, phones, decades, names, fixed expressions and times. Exact times and o’clock differ. A value alone does not prove its role or pronunciation; no numeric rewrite is offered.
Accepted by this check At dawn
A number without established context , with trigger and fix details
Avoid disruptive midphrase backing/echo placement
Avoid disruptive midphrase backing/echo placement; significant backing material can appear at line end or separately.
What LyricLint can establish
Does not provide a reliable text-only echo-deletion predicate. Preserve until role/placement is established.
Use original Japanese script even when release metadata is romanized
Use original Japanese script even when release metadata is romanized; do not add furigana/readings, including unusual readings. Artist-selected kanji matter; use Japanese glyph forms rather than Chinese variants.
What LyricLint can establish
Header-English policy on Genius is unrelated. Distinguish pronunciation glosses from actual backing vocals before any removal; no global Han-character normalization.
Structure belongs in tagging. Explicit A-melody/pre-chorus/chorus labels have stated mappings
Structure belongs in tagging. Explicit A-melody/pre-chorus/chorus labels have stated mappings; B-melody, solo and C-melody labels each allow more than one target. Intro/outro refer to sung sections, not pure instrumental edges.
What LyricLint can establish
Some explicit source labels support mapping; ambiguous labels require choice. Preserve source labels and musical identity.
Halfwidth spacing/commas can aid phrasing and readability
Halfwidth spacing/commas can aid phrasing and readability; line breaks follow meaning and singability.
What LyricLint can establish
No automatic spacing at every script boundary or split at a fixed character count.
Vocalization spelling and Katakana/Latin choice depend on pronunciation, ordinary usage and official lyrics
Vocalization spelling and Katakana/Latin choice depend on pronunciation, ordinary usage and official lyrics; repeated vocables can use hyphens/spaces/line breaks by phrasing.
What LyricLint can establish
No universal romanization/interjection replacement or separator.
Separate blocks with blank lines, but says a blank is not needed immediately after #INSTRUMENTAL
Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.
What LyricLint can establish
Directly conflicts with MX-S12 requiring that blank. Do not silently select an automatic spacing policy.
Checks for this convention
An instrumental interval needing review
Requires review under this check We sing #INSTRUMENTAL We return
Musixmatch uses this marker only for more than fifteen consecutive seconds without qualifying lyrics between separately tagged sections, never inside a section or at a track edge. Whole-track instrumental status is separate. Text or two lyric-start times cannot prove the interval.
Accepted by this check We sing We return
An instrumental interval needing review , with trigger and fix details
Lists Latin line starts, proper nouns/acronyms and parenthetical beginnings among capitalization cases
Lists Latin line starts, proper nouns/acronyms and parenthetical beginnings among capitalization cases; rejects arbitrary all-caps/all-lowercase/title-case presentation.
Guidelines disagree. The official sources behind this convention state different requirements. LyricLint preserves your wording and lists each source above rather than choosing one for you.
What LyricLint can establish
Parenthetical wording differs from main grammatical-only guidance; exact mixed-script/parenthetical scope needs resolution.
Checks for this convention
Capitalized backing vocals
Flagged example We return (Yeah)
Ordinary English backing-vocal openings use lowercase inside a lyric line. Pronouns, names and new sentences keep their grammatical capitals.
Accepted by this check We return (yeah)
Fix: Lowercase “Yeah”
Capitalized backing vocals , with trigger and fix details
A lowercase line beginning
Flagged example we return
Musixmatch capitalizes lyric line beginnings. Preserve established name casing and review mixed-language context before changing it.
Accepted by this check We return
Fix: Capitalize w
A lowercase line beginning , with trigger and fix details
Expressive capitals needing review
Requires review under this check WE RETURN AGAIN
Musixmatch does not use all-caps for shouting or arbitrary title case. Names, acronyms, German nouns and embedded languages require context; no automatic lowercasing is offered.
Accepted by this check We return again
Expressive capitals needing review , with trigger and fix details
Children's lyric kanji/kana choices depend on intended age
What LyricLint can establish
Audience metadata/human judgment; no universal all-kana conversion.
Avoid excessive Japanese corner quotes in dialogue
Avoid excessive Japanese corner quotes in dialogue; line breaks/halfwidth spaces/parentheses can support long spoken content.
What LyricLint can establish
General comma-plus-quotes treatment is not a universal Japanese conversion.
Use fullwidth question/exclamation marks after fullwidth preceding characters, ASCII forms after halfwidth characters
What LyricLint can establish
Define and review width classification for mixed scripts and punctuation; no NFKC normalization of the whole draft.
Checks for this convention
A Japanese punctuation width mismatch
Flagged example 帰る?
The Japanese Musixmatch FAQ uses fullwidth question and exclamation marks after fullwidth characters and ASCII marks after halfwidth characters. Only this mark changes; lyric scripts and other character forms stay exact.
Accepted by this check 帰る?
Fix: Use ?
A Japanese punctuation width mismatch , with trigger and fix details
Where strict sentence alignment fails, meaning may be redistributed over its existing two or three lines while total line count stays fixed
What LyricLint can establish
Qualifies the main translation instruction. Preserve translation alignment; linguistic translation remains outside the transformer.
Native-script lyrics and romanized forms in the Translation surface are distinct. Editing automatic romanizations is restricted to high-rank Curators. The current article gives no usable complete per-language romanization list
What LyricLint can establish
Preserve content kind and script. Do not claim that Arabic/Korean automatic romanization is available from this page title.
Translation must be personally authored, not copied or machine-translated, with context and original untranslatable terms preserved
What LyricLint can establish
Document scope; the deterministic format engine does not translate lyrics.