Forum Discussion

mahesh_revanwar's avatar
mahesh_revanwar
Expert
10 years ago

Html entity getting encoded to the special character.

Hi,

 

We are facing a issue with character en-codeing of "&nbsp". This space(&nbsp) char is get converted to special charecter on chrome.

We have searched for this issue on google forums.

 

https://productforums.google.com/forum/#!topic/chrome/ULF0TFuEmPU

 

They told us to remove helvetica font file.

 

But we have a removed all helvetica font family from CSS but still the issue occur.

Is this Helvetica font OOB supported by lithium? 

If yes then how to remove this?

 

Can anyone guide, how can we overcome this issue.

 

 

Thanks & Regards,

Mahesh Revanwar

 

  • PaoloT's avatar
    PaoloT
    Lithium Alumni (Retired)
    10 years ago

    Hi mahesh_revanwar 

     

    could you provide some context? Is this being done in a custom component, or in an endpoint, or elsewhere? Maybe you could share some code and what you are trying to accomplish in order to understand better the problem.

     

    Thanks,

    • mahesh_revanwar's avatar
      mahesh_revanwar
      Expert
      10 years ago

      Hi PaoloT ,

       

      This seems to be font issue which appers in OOB component.

      Initially we were using Helvetica font for community and now we are changing this Helvetica font to GothamMedium font.

       

      As per our observation it happen only for GothamMedium font.

       

      Please find attachement for the screen shot of page.

       

      Thanks & Regards,

      Mahesh Revanwar


      Font Issue on Chrome.PNG
      • PaoloT's avatar
        PaoloT
        Lithium Alumni (Retired)
        10 years ago

        Hi mahesh_revanwar ,

         

        font rendering issues of a standard HTML entity such as   are not really caused by Lithium. It will be a behavior / bug of the rendering client (in this case, the Chrome web browser) or an issue with the client machine itself. I believe OlivierS  already ponited out a possible cause - keep us posted if you manage to find out what the issue was on your client.

         

        Thanks,