Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Checklist to introduce multibyte fixes #3

Open
8 of 10 tasks
miya0001 opened this issue Jul 2, 2018 · 1 comment
Open
8 of 10 tasks

Checklist to introduce multibyte fixes #3

miya0001 opened this issue Jul 2, 2018 · 1 comment

Comments

@miya0001
Copy link
Collaborator

miya0001 commented Jul 2, 2018 •
edited
Loading

Following is the checklist to open track tickets for multibyte fixes for WordPress.

  • The length of the excerpt should be 110 in Japanese.
  • The length of the excerpt in RSS should be 110 in Japanese.
  • Double-width space should be used as search delimiter.
  • Email should be encoded with ISO-2022-JP
  • Characters in pingback and trackback should not be broken.
  • The filename which is in Japanese should be encoded md5.
  • The length of comment in dashboard should be 40.
  • The length of draft in dashboard should be 40.
  • Incremental search of link in tinymce should fire from 2 chars.
  • We don't need italic in dashboard.

Related:
@miya0001 miya0001 changed the title Checklist to introduce multibyte fixes to open tickets. Checklist to introduce multibyte fixes Jul 2, 2018
@miya0001
Copy link
Collaborator Author

miya0001 commented Jul 9, 2018

List of tickets

https://docs.google.com/spreadsheets/d/13oGbc7AqEN6OUvmze-JDCKXDdruFqsxqSAdI7-b6Lho/edit#gid=0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@miya0001