Non-standard question mark

The fullwidth question mark '？' (U+FF1F) looks like the ASCII '?' (U+003F) but is a different Unicode character. It often appears after copying from East Asian sources or using certain IMEs and can break searches, grammar tools, and layout in English documents.

Quick fix: replace U+FF1F with U+003F, then check for nearby fullwidth spaces or punctuation that may have traveled with it.

Quick answer

Replace the fullwidth question mark '？' (U+FF1F) with the standard ASCII question mark '?'. Then scan for fullwidth spaces or punctuation and normalize them.

Fullwidth '？' is correct in Chinese and Japanese, but not in English texts.
Copy the literal '？' from here and use Find-and-Replace to swap it for '?'.
Add a simple automation (find-and-replace, linter rule, or commit hook) for English files to prevent recurrence.

Core explanation: what's the difference in one line

The ASCII question mark '?' is U+003F; the fullwidth mark '？' is U+FF1F. They look similar but are different code points, so tools and fonts treat them differently.

U+003F = '?' (use in English).
U+FF1F = '？' (standard in many East Asian languages).
Different code → different behavior in search, grammar checkers, and rendering.

Why it breaks things: searches, grammar checkers, and exports

Because the characters differ, literal searches miss matches, sentence-splitting can fail, and exports (PDF, EPUB) may show odd spacing or line breaks.

Search miss: searching for '?' won't find '？'.
Grammar tools that rely on ASCII punctuation may miss sentence boundaries.
Exports can show unexpected line wrapping or spacing because fullwidth punctuation behaves like CJK glyphs.

Search-fail: You search for "How do I reset?" but the file uses "How do I reset？" - no match.
Grammar-miss: A checker may miss a sentence end after "Are you ready？" and fail to flag the next sentence's capitalization.

Spacing and adjacent punctuation - clean up after replacing

Fullwidth punctuation often appears alongside fullwidth spaces (U+3000) or other fullwidth marks. Replace the question mark, then normalize surrounding punctuation and spaces.

Look for fullwidth space U+3000 (visually wider than a normal space).
Check for fullwidth comma '，', fullwidth period '。', and fullwidth exclamation '！'.
Normalize quotes (curly vs straight) only if the document is in English.

Spacing-broken: "Are you free？ I'll call you." → "Are you free? I'll call you."
Quotes: Wrong: "Are you sure？" →
Right: "Are you sure?"

Hyphenation, line breaks, and character width (hyphenation)

Fullwidth characters follow CJK line-breaking rules and can force awkward breaks in narrow columns or justified text. Fix these before finalizing PDFs or print layouts.

Fullwidth marks can block normal English hyphenation and wrapping.
Replace them before creating print-ready files to avoid single-character lines or odd spacing.
Check sidebars and narrow columns after normalization.

Layout-issue: A paragraph ends "...we will decide？" and the mark drops to its own line in the PDF-replace with '?' to restore normal wrapping.

Grammar note: question marks and sentence endings (grammar)

After replacing the character, confirm the sentence is actually a question. Some fragments need a rewrite. Also check punctuation placement with quotes and abbreviations.

A question mark ends a direct question: "Are you ready?"
When a sentence and a short question sit together, consider splitting: "Is it ready? If so, send it."
American style places the question mark inside quotes if the quoted material is a question: He asked, "When will you arrive?"

Clarify: Wrong mark: "Available later？" → Replace and rewrite: "Are you available later?"

Try your own sentence

Test the whole sentence instead of an isolated phrase: context makes the right punctuation clearer.

Examples you can copy: wrong → right (work, school, casual and extra pairs)

Wrong→right pairs grouped by context. Copy the corrected lines into your editor to replace quickly.

Work - wrong: Could you review the attached draft？
Work - right: Could you review the attached draft?
Work - wrong: When is the status meeting？
Work - right: When is the status meeting?
Work - wrong: Do we have budget approval？
Work - right: Do we have budget approval?
School - wrong: Did you finish the homework？
School - right: Did you finish the homework?
School - wrong: What is the thesis statement of this essay？
School - right: What is the thesis statement of this essay?
School - wrong: Solve question 5？ Show steps.
School - right: Solve question 5. Show your steps.
Casual - wrong: Dinner later？
Casual - right: Dinner later?
Casual - wrong: You coming tonight？
Casual - right: You coming tonight?
Casual - wrong: New post up？ Check link in bio.
Casual - right: New post up? Check link in bio.
General - wrong: "Are you sure？" she asked.
General - right: "Are you sure?" she asked.
General - wrong: (Everything ready？)
General - right: (Everything ready?)
Contraction - wrong: What's the plan for tomorrow？
Contraction - right: What's the plan for tomorrow?

Rewrite help: step-by-step fixes and quick rewrites

Checklist: Find → Replace → Normalize → Recheck. If the sentence still sounds off, use these rewrite patterns.

Step 1: Find the literal '？' (copy it) and replace with '?'.
Step 2: Replace fullwidth space U+3000 and fullwidth commas/periods.
Step 3: Run grammar/style checks; if meaning is unclear, rewrite for clarity.

Rewrite-1: Original: "You available to present at 2 pm？" → Replace +
rewrite: "Are you available to present at 2 p.m.?"
Rewrite-2: Original: "Finished the draft？ Let me know." →
Rewrite: "Have you finished the draft? Let me know."
Rewrite-3: Original: "Project delayed？ We should update the stakeholders." → Rewrite into two sentences: "The project is delayed. Should we update the stakeholders?"
Rewrite-4: Original: "Client OK with design？" → Better: "Is the client OK with the design?"

Real usage and tone: when not to change '？' (real_usage)

Keep '？' in original Chinese or Japanese text. In bilingual documents, normalize only the English-labeled sections to avoid corrupting native text. Informal social posts sometimes use fullwidth marks stylistically-optional, not standard English.

Do not change punctuation inside Chinese or Japanese sentences.
For bilingual pages, run normalization only on English blocks.
Stylistic use on social media is acceptable but nonstandard for formal English.

Bilingual: 今天开会几点？ We will follow with an English agenda below.
Stylistic: "New post？ Check it out." - fine as style, not standard English.

Memory trick: spot the fullwidth mark fast

Use quick visual checks or a character inspector. In monospaced fonts, fullwidth characters often occupy two columns. If spacing looks off, paste the mark into a Unicode inspector to confirm U+FF1F.

Monospace test: fullwidth often spans two columns.
Copy the mark and check a character-info tool for U+FF1F.
Search your file specifically for '？' when scanning for invisible punctuation.

Quick-test: Paste the mark into a character-info tool; if it reports U+FF1F, replace it with U+003F.

Similar mistakes to watch for

When you spot a fullwidth question mark, expect related issues: fullwidth comma '，' (U+FF0C), fullwidth period '。' (U+3002), fullwidth exclamation '！' (U+FF01), non-breaking spaces (U+00A0), or fullwidth spaces (U+3000). Normalize them together.

Fullwidth comma '，' → ','; fullwidth period '。' → '.'
Non-breaking space U+00A0 or fullwidth space U+3000 → normal space
Curly smart quotes vs straight quotes: pick a style and normalize for English content

Similar: Wrong: "Hello，world！" →
Right: "Hello, world!"

FAQ

Why do I get a fullwidth question mark when I paste text?

Copying from East Asian webpages, PDFs, or some messaging apps preserves the original Unicode characters. The pasted text keeps U+FF1F rather than ASCII '?'.

How do I find the fullwidth question mark in my editor?

Copy the fullwidth '？' from this page and paste it into your editor's Find box. Because its code point differs from '?', a literal find-and-replace will catch it. Some editors accept Unicode escapes (U+FF1F) in searches.

Will grammar and spell checkers flag a fullwidth question mark?

Sometimes they flag resulting errors (missed sentence boundaries or spacing), but not always the character itself. Normalize punctuation first, then rerun the checker.

Should I ever keep '？' in an English document?

Only when preserving original Chinese or Japanese text inside an English document. For English-language sentences, replace it with ASCII '?'.

How can I prevent this from happening again?

Use an English keyboard or IME while writing English, add a find-and-replace script or linter rule for U+FF1F, and run a normalization step before publishing.

Want help checking a sentence?

Unsure whether a sentence contains fullwidth marks or other invisible Unicode issues? Paste it into a grammar tool and run a normalization pass first. That removes hidden punctuation bugs and fixes spacing and sentence-boundary problems.