i wrote the following code in my application which is in MS Access, to display a message box in Farsi language(non-English language), but while i am typing in Farsi(Persion) it types in some special/unknown/different characters, and also while i run the application the message box displays that special/different characters instead of "احمد" which i want to be display.
msgbox("احمد")
any help well be my pleasure, and i really need for any kind of reply and help pleaseeeee.
Might check into unicode options for the controls you're using.
Edit: Based on a bit of googling I did, there doesn't seem to be any unicode support built in to msgbox (surprise to me), but other controls do support it by default apparently, leading to custom solutions. See below for links.
A forum post I found mentions a custom msgbox creator:
http://www.pcreview.co.uk/forums/msgbox-wont-display-unicode-characters-t2766299.html
Another post discussing how to make forms that will display a unicode message:
http://groups.google.com/group/microsoft.public.access/browse_frm/thread/4f2cd646023e0054/892dfd73309ad76b
Related
I am creating a website in German. No big deal I am nativ speaker.
If I misspell "Mittelsmann" by left the last character I have this suggestion from chrome:
This is usefull and I like to keep this behavior. But this input-field is an exception because it requires a scientific value and should be in english, so all suggestions for german words are basically wrong (call to Seiri of Kaizen).
Question: How can I force the suggestion to be in english for this input field ONLY?
That is a very good question. I'm German myself and ran into the same problem last year.
There are suggestions to let the HTML lang attribute decide which spellcheck is used (see the chromium developer discussion ending with WontFix/Closed). But sadly a lot of the current browsers (especially native browsers of the OS, and all mobile keyboards of cause) use the external spell checking provided by the OS.
So your wanted feature doesn't exist (resp. no standard for that), because a customized/picked language by JavaScript is often not transferable to the spell checker.
I solved my problem by adding and activating both languages German and English to my spell checker in Google Chrome, which resulted in getting both suggestions. That's not satisfying, but it worked for me.
Edit:
I also see a lot of German sites solving that problem by using attributes like autocorrect="off", autocapitalize="off" and spellcheck="false" on an "just English" input field to avoid confusing the user by German spelling suggestions and corrections. May that be an option to you?
I'm trying to store some text containing html tags into properties, which doesn't work. I created a form for a property with the data type 'text' and a template. Saving the form writes the text into the template, but it can't get displayed, as it contains illegal characters, as I guess.
What I'm trying to do:
I need a form to enter data, containing html tags and special
characters
I'd like to be able to use a query to find all those pages
and show that text using a template I provide to the ask query.
I also tried to use the free text option, but then I can't retrieve it using the ask query.
What would be the best, or at least a working solution to this?
Thanks a lot
storing text with html tags is a bit tricky in SemanticMediaWiki
The reason is the invention of the StripMarkers UNIQ/QINU by the MediaWiki developers.
When parsing the content of page with html tags in it the parsing is sort of "postponed". This technical detail unfortunately makes it hard for extension developers like the SMW developers to solve the issue of handling such content. Also it makes it hard for lay people to follow the discussion on how to solve the problem
Here are two examples of SMW Issues that are marked as "closed". This state of affairs means that by following the configuration hints in the issue your problem should be solved. If not please ask a question on the SMW issue list or even initiate the reopening of the issues.
https://github.com/SemanticMediaWiki/SemanticMediaWiki/pull/794
https://github.com/SemanticMediaWiki/SemanticMediaWiki/issues/3707
On my wiki we ran into this and resolved it by replacing special characters (we had issues with [ ] =, but the same problem happens with to < > tags too) with alternate unicode characters using the regex extension and a template before setting the property with {{#set:}}. If you want to display the formatted text on the wiki directly then call that parameter separately without replacing the unicode characters.
When you want to display the property, you can then run the reverse replacement with regex before displaying your now intact code (using the template result format to allow you to perform the operation on the output of the query).
To switch to special characters you can create this template
{{#regex:{{#regex:{{#regex:{{#regex:{{#regex:{{{1|}}}|/=/|꞊}}|/\[/|［}}|/\]/|］}}|/>/|≽}}|/</|≼}}
And to switch back you can use this as a template
{{#regex:{{#regex:{{#regex:{{#regex:{{#regex:{{{1|}}}|/꞊/|=}}|/［/|[}}|/］/|]}}|/≽/|>}}|/≼/|<}}
I have looked into the previous postings to do with this area but haven't found any relevant answers as perhaps I am asking the wrong question.
On the popular design site Dribbble, there seem to be interesting formatting changes in profile names that break from the conventions of the site's styling.
Alot of people have been adding special characters (ΔδΓ etc.) that can be achieved by pasting into their profile form and saving changes, yet some users have somehow managed to enter formatted versions of their name, despite the profile form not supporting HTML or Markdown. You can see an example in the images below.
An example of copying the font to Google with maintained formatting
When opening in inspector, it also shows the formatted type
How could this be done in a simple text input form that doesn't support HTML/Markdown?
These are almost certainly Unicode characters, just like these characters that you reference in your question: ΔδΓ.
For example, Unicode's mathematical alphanumeric symbols section includes symbols that look like the ones in your screenshot. Since these are separate Unicode characters there is no need for additional formatting.
Users will need to have a font that supports those characters installed locally to view them.
First of all sorry for this perhaps silly question. But I'm trying to figure out if the <dir="rtl"> attribute really is mandatory when displaying arabic characaters on a web page.
I've searched for a while now on this subject but I'm still puzzled. The W3C website states: "If a document contains right-to-left characters, and if the user agent displays these characters, the user agent must use the bidirectional algorithm." Source: https://www.w3.org/TR/html4/struct/dirlang.html
As far as I understand the above text this means that you will have to use <dir="rtl"> attribute but I can't find out why exactly.
The reason I'd like to know is that we have to create a 'somewhat' arabic version of a page without spending too much time on aligning and mirroring the whole website.
Does somebody know why the <dir="rtl"> attribute is mandatory? Or why it maybe why it is not mandatory? The more I read about it the more it starts messing with my head and I have a hard time finding a clear answer.
Kind regards,
Jan-Willem
This is mandatory because; 1. Its makes bots and users know how what language your page uses. 2. Its would display the text according to how that language is expected to be, rtl is mearnt for arabic and/or hebrews.
I've been grappling with the fraught area of escaping user (text) input for web pages. The ultimate goal is to have user input displayed and stored exactly as typed in, without breaking anything.
To that end I have been using the following test string :
'"_$%^&*()+=-£{}[]/n/<>\#~;|,.?#:!&``"'
It seems to work well (even Stack Overflow or Twitter is not immune, hence the back ticks). My question is, will this string capture most escaping problems, for example going from a web page via Ajax and to a database and back again?
In fact how do I display this string in Stack Overflow without the back ticks?
Is there a better one, e.g. say one that will highlight encoding problems too?
When I'm testing, I'm using something like this
a’b<’>",!"/%$?$&?%(()%/"!"/&?%$/"&$/"?%&?-f¯Ñ112üêù
This is generally sufficient to highlight encoding issues, at least from what I can see.
Including a mathematical symbol such as unicode x2202 might be useful too.
That seems like it should be all of them. The smartest thing to do would be to (depending on the language you're using) use a library that has been well tested, that can sanitize user input. Just ask around what other websites use.
See here: http://gendoh.com/2511063
The post itself is written in Korean, but you could see what makes difference between several given patterns. (V1 to V3 are for generic web apps while V4 and V5 is for javascripts.)