Skip to content

docs: clarify Google Docs API Unicode behavior for smart chips (fixes #2547) #2673#2674

Open
subash-c wants to merge 1 commit intogoogleapis:mainfrom
subash-c:fix/issue-2547-with-description
Open

docs: clarify Google Docs API Unicode behavior for smart chips (fixes #2547) #2673#2674
subash-c wants to merge 1 commit intogoogleapis:mainfrom
subash-c:fix/issue-2547-with-description

Conversation

@subash-c
Copy link

  • The \ue907 character is intentional Google Docs API behavior, not a bug. This addresses user confusion by:
  • Adding comprehensive documentation explaining the Unicode placeholder behavior
  • Providing a working example showing how to extract actual date/chip data
  • Demonstrating best practices for working with richLink properties
  • Clarifying that this is API design, not a client library issue
  • The Google Docs API intentionally replaces non-text elements (smart chips, dates, people, etc.) with Unicode Private Use Area character U+E907 in TextRun.content, as documented in the API specification. The actual data is available in richLinkProperties within the same document elements.

This is an educational contribution to help developers understand expected API behavior and implement proper workarounds.

…oogleapis#2547)

The \ue907 character is intentional Google Docs API behavior, not a bug.
This addresses user confusion by:

- Adding comprehensive documentation explaining the Unicode placeholder behavior
- Providing a working example showing how to extract actual date/chip data
- Demonstrating best practices for working with richLink properties
- Clarifying that this is API design, not client library issue

The Google Docs API intentionally replaces non-text elements (smart chips, dates,
people, etc.) with Unicode Private Use Area character U+E907 in TextRun.content,
as documented in the API specification. The actual data is available in
richLinkProperties within the same document elements.

This is an educational contribution to help developers understand expected
API behavior and implement proper workarounds.
@subash-c subash-c requested review from a team as code owners October 14, 2025 09:31
@product-auto-label product-auto-label bot added the size: l Pull request size is large. label Oct 14, 2025
@Gumelar1922
Copy link

https://colab.research.google.com

@Gumelar1922
Copy link

https://colab.research.google.com

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size: l Pull request size is large.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants