non-english

in sql developer--preference Environment--encoding is already set to 'UTF-8' Code Editor--fonts was set to 'Verdana' Database--NLS--Language was set to 'American' The data in db was written by Java in UTF-8 encoding (95% percent sure） What else I need to do to make it displayed correctly? Note: the squares characters are actually Chinese characters. Problem solved. Using font 'Microsoft YaHei' sqldeveloper uses the system fonts from the host machine. On my Win8 system there is a font that has glyphs for very many unicode characters and thus works for many unicode characters. 'Arial Unicode MS'

I am using Primefaces 3.2. I've got problems with using primefaces fileDownload. I can upload the files and keep their non-english name on the server (in my case this is Russian). However, when I use p:fileDownload to download the uploaded files I cannot use Russian letters since they get corrupt. It seems that the DefaultStreamedContent class constructor accepts only Latin letters. I am doing everything according to the showcase on the primefaces website as shown below. public FileDownloadController() { InputStream stream = ((ServletContext)FacesContext.getCurrentInstance().getExternalContext

I have some strings that have a mix of English and none English letters. For example: w='_1991_اف_جي2' How can I recognize these types of string using Regex or any other fast method in Python? I prefer not to compare letters of the string one by one with a list of letters, but to do this in one shot and quickly. Salvador Dali You can just check whether the string can be encoded only with ASCII characters (which are Latin alphabet + some other characters). If it can not be encoded, then it has the characters from some other alphabet. Note the comment # -*- coding: .... . It should be there at

If it's possible, should I accept such emails from users and what problems to expect when I will be sending mails to such addresses? Yuval Adam Officially, per RFC 6532 - Yes . For a quick explanation, check out wikipedia on the subject. Update 2015: Use RFC 6532 The experimental 5335 has been Obsoleted by: 6532 and this later has been set to "Category: Standards Track", making it the standard. The Section 3.2 (Syntax Extensions to RFC 5322 ) has updated most text fields to include (proper) UTF-8. The following rules extend the ABNF syntax defined in [RFC5322] and [RFC5234] in order to allow