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.

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

Use bytcode sequence for unicode ellipsis #945

Merged
merged 1 commit into from Nov 9, 2012
Merged

Use bytcode sequence for unicode ellipsis #945

merged 1 commit into from Nov 9, 2012

Conversation

aleho
Copy link

@aleho aleho commented Nov 9, 2012

The codepoint for "horizontal ellipsis" is 0x2026, which enables a more
robust display of that character on different systems.

With my setup here (Firefox, Linux, Helvetica) ellipsis was not displayed correctly (replaced by a question mark indicating a missing character).

I'm not entirely sure about all that UTF stuff, but this should likely work on most modern systems I guess.

The codepoint for "horizontal ellipsis" is 0x2026, which enables a more
robust display of that character on different systems.
@dereuromark
Copy link
Member

you accidently committed something else, as well.

@aleho
Copy link
Author

aleho commented Nov 9, 2012

Yeah, I always forget that github uses branches, not commits, for pull requests. Makes sense, I don't.

markstory added a commit that referenced this pull request Nov 9, 2012
Use bytcode sequence for unicode ellipsis

Fixes #3356
@markstory markstory merged commit 7e00be8 into cakephp:2.3 Nov 9, 2012
@ADmad
Copy link
Member

ADmad commented Nov 9, 2012

This PR causes failed tests case. The character code used seems to actually cause more display problems as seen here and here.

@ADmad
Copy link
Member

ADmad commented Nov 9, 2012

Perhaps the display issue is because those are console outputs but the test cases surely need to be updated.

@dogmatic69
Copy link
Contributor

I updated my cake repo yesterday and noticed this issue, was going to check out the cause but saw this come up. This commit has fixed it for me

@markstory
Copy link
Member

I'll take a look as I merged that change in.

@aleho
Copy link
Author

aleho commented Nov 10, 2012

I had a commit locally that addressed the tests but completely forgot about it. Who needs test cases anyway? ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants