Joomla 2.5 with Sobi Pro and Mandarin characters - joomla

My client has a single page on his Joomla! 2.5 site whose content must be translated into Mandarin. In text areas within Sobi Pro, we can easily add the Mandarin text, and all is fine, but in text fields, we are unable to add the text - we get a bright red validation error with the text "The data entered in the "area name" field contains not allowed characters".
How can I make it work so that I can enter Chinese characters in these text fields?
Thanks!
Kobus

Found out by means of a person on the Sobi Pro website; it was a filter that prevented input of the characters. Problem is solved.
Thanks!
Kobus

Related

Node wont save if text field contains word "having"

When I try to save edited node Drupal just reset field values and do nothing without any error message or log.
I entered text word by word and found that word "having" cause such behavior.
I'm using ckeditor to edit and filter text value and I guess that this module source of problem. As if I save text as plain text there are no issues.
Right now I don't know what to do next to track, dig deeper and isolate this issue...
PS. In ckeditor format settings I checked only two options:
Limit allowed HTML tags and correct faulty HTML
Convert line breaks into HTML (i.e. br and p)

Displaying vCard photos in Windows Contacts

Following vCard 2.1, I'm adding photos to vCards. I'm encoding the image fetched from a URL, then adding the encoded value to the proper place within the vCard. This seemingly displays the photo correctly for all programs that can open vCards except the Windows Contacts program on Windows 7 (probably doesn't work for newer versions of Windows either).
As far as I can tell, the below snippet should display the vcard photo when opened in Windows Contacts:
BEGIN:VCARD
VERSION:2.1
N;CHARSET=ISO-8859-1:Lastname;Firstname;
FN;CHARSET=ISO-8859-1:Firstname Lastname
ORG;CHARSET=ISO-8859-1: Organization LLP
PHOTO;ENCODING=b;TYPE=jpg: <base64 encoded image as one line>
TITLE;CHARSET=ISO-8859-1:Position
TEL;WORK;VOICE:+1 999 999 9999
END:VCARD
All the other information displays in Windows Contacts, but not the photo. The standard blank image placeholder displays.
I have tried
ENCODING=BASE64
ommitting the ENCODING keyword altogether
removing the TYPE keyword altogether
using specifically a 240px by 240px image
adding the image URL value in the file instead of the encoded value
Anyone have any ideas?
Version 2.1 uses ENCODING=BASE64.
Put an empty line after the PHOTO property. Outlook requires this, so Contacts might too.
Put all parameter names/values in upper case. I know of one compatibility problem with Windows Contacts where it doesn't recognize a parameter value if it's in lower case.
Remove the space character before the base64 data.
Try setting the TYPE parameter to JPEG.
You've correctly encoded the image data, right? Try using an online decoder to make sure.
Corrected property:
PHOTO;ENCODING=BASE64;TYPE=JPEG:<base64 encoded image as one line>
[empty line]
According to the specs, if you have a URL, you should set the VALUE parameter to URL.
PHOTO;TYPE=JPEG;VALUE=URL:<url goes here>
I've run into your post while researching this question and I was able to successfully find the correct way to achieve this.
Bellow is a self-containing example of a v-card containing an 96x96 embedded red.gif image as the PHOTO.
https://www.rfc-editor.org/rfc/rfc2426#section-3.1.4
Be sure to note the VERSION line and the PHOTO line. This is currently working in Outlook365.
BEGIN:VCARD
VERSION:3.0
N:Gump;Forrest;;Mr.;
FN:Forrest Gump
ORG:Bubba Gump Shrimp Co.
TITLE:Shrimp Man
PHOTO;ENCODING=BASE64;TYPE=GIF:R0lGODdhYABgAPAAALccHMlFJiH5BAEAAAEALAAAAABgAGAAAAJuhI+py+0Po5y02ouz3rz7D4biSJbmiabqyrbuC8fyTNf2jef6zvf+DwwKh8Si8YhMKpfMpvMJjUqn1Kr1is1qt9yu9wsOi8fksvmMTqvX7Lb7DY/L5/S6/Y7P6/f8vv8PGCg4SFhoeIiYqLiIUgAAOw==
TEL;TYPE=work,voice;VALUE=uri:tel:+1-111-555-1212
TEL;TYPE=home,voice;VALUE=uri:tel:+1-404-555-1212
ADR;TYPE=WORK;PREF=1;LABEL="100 Waters Edge\nBaytown\, LA 30314\nUnited States of America":;;100 Waters Edge;Baytown;LA;30314;United States of America
ADR;TYPE=HOME;LABEL="42 Plantation St.\nBaytown\, LA 30314\nUnited States of America":;;42 Plantation St.;Baytown;LA;30314;United States of America
EMAIL:forrestgump#example.com
REV:20080424T195243Z
x-qq:21588891
END:VCARD

unusual error occur in laravel validation

In my laravel 4 project i gave a validation like this
'contact_no' => 'numeric|digits_between:10,10',
But this shows error in a weird situation. If I copy and paste the phone number in the field it shows validation error "The contact no must be a number." But when I type the phone number everything is fine.
Did anyone knows why laravel shows this kind of error? and how I can resolve this?
The screen shot is:
If you copy a string from a source which is not plain text (but formated text) sometimes there are invisible spaces copied along with the string. I had this strange behavior several times.
How you test it
Open notepad (or any plain text editor)
Type your number
Copy it from there
Paste it in your form
I guess this number will work.
How you could try to go around this problem
Before validation trim the input data from contact_no to remove all whitespaces first. See http://php.net/manual/en/function.trim.php

Breezing Forms Joomla- Japanese content displayed as question marks(?)

I'm using Breezing forms and building a Japanese website..All the contents are displayed in Japanese except for the select boxes and check boxes which display ???? instead of characters..
Please Help
Thanks in Advance

Drupal 7: HTML tags stripped for every input format, even PHP format

I have a Drupal 7 installation, multilingual. No matter which input format i'm choosing for the node body, every HTML tag is stripped. The input format is well configured. It's like Drupal always uses Plain Text as Filter, even if Full HTML is selected.
I found the answer in the Drupal Forum:
https://drupal.org/node/1829860
For the records: After some searching I found the culprit: I defined a
custom display setting for the content type article
(/admin/structure/types/manage/article/display) and changed (by
mistake) the field format to "plain text" for the body text. Reverting
to "default" fixed the problem.

Resources