Dev.SN

utf-8 char test - direct character entry -

posted by martyb on Thursday April 30 2015, @09:28AM   
from the text-test dept.

cf: https://github.com/SoylentNews/rehash/issues/29#issuecomment-97700440

Subject: Re: [rehash] Server Error when preview comment having char

Message: I can't reproduce this anymore; I copy and pasted in quite a few single unicode characters, including 0x7f (division sign), and failed to get the server to up and chuck. I think we can close this, but I'd like @martyb to reconfirm it

Attempting same, here.

pewp 💩

• utf-8 character test - direct entry utf-8 character test - direct entry (Score: 2) by martyb on Thursday April 30 2015, @11:20AM

  by martyb (76) on Thursday April 30 2015, @11:20AM (#28403) Journal

  utf-8 character test - direct entry:

  I entered the characters represented by:

  000000  10 5f 11 5f 12 5f 13 5f  14 5f 15 5f 16 5f 17 5f  >._._._._ ._._._._<
  000010  18 5f 19 5f 1a 5f 1b 5f  1c 5f 1d 5f 1e 5f 1f 0d  >._._._._ ._._._..<
  000020  0a                                                >.<

  which might be better recognized as:

  ^P_^Q_^R_^S_^T_^U_^V_^W_^X_^Y_^Z_^[_^\_^]_^^_^_

  I accepted the selection: "HTML Formatted", and pressed "Preview", I received:

  OK
  
  The server encountered an internal error or misconfiguration and was unable to complete your request.
  
  Please contact the server administrator, slash@dev.soylentnews.org and inform them of the time the error occurred, and anything you might have done that may have caused the error.
  
  More information about this error may be available in the server error log.

  Starting Score:	1		point
  Karma-Bonus Modifier		+1
  Total Score:		2

• Re:utf-8 character test - direct entry (Score: 2) by martyb on Thursday April 30 2015, @11:37AM

  by martyb (76) on Thursday April 30 2015, @11:37AM (#28404) Journal

  NOTE: The parent comment is reporting the attempt to directly enter the *characters* which correspond to the hexadecimal character entities from 0x10 through 0x1f, with each character separated from the next by an underscore character "_" (i.e. &#x5f;)

  &#x10;_&#x11;_&#x12; ... &#x1f;

  i.e.:

  �_�_� ... �

  NOTE: SoylentNews *currently* replaces these characters entered as numeric character entities with the character "&#65533;" — this is correct behavior.

  The problem is that it is failing to do so for these characters when they are entered directly. These are illustrative of the problem with Unicode characters from Control Set C0 and Control Set C1.

  Parent