In Rundeck section "Log Output" I see question symbols instead of Russian letters in the text of log.
Where can I configure the correct display of Russian characters in the Log Output.
It seems that you need to set UTF-8 as default encoding at the moment of start Rundeck, try adding RDECK_JVM_OPTS="-Dfile.encoding=UTF-8" on the rundeckd file, take a look at this (please do no edit the profile file directly). Here you can see the same issue on GitHub, especially this comment.
Related
While I was using Burp I noticed that it has problem to show Hebrew characters.
Reproduce:
Open Burp Professional, go to Dashboard and start a "New scan".
Enter the following URL (as an example):
https://blog.ravmilim.co.il
After couple of seconds it will show you the results in the Target tab:
In the "User options" tab I changed the Font and the "Character Sets" to UTF-8 but it still the same.
Any idea how it can be solved?
simply change the font to Courier new.
I use Inno Setup 5.5.9 Unicode to create installation package for my app.
To show EULA I use this line in *.iss:
LicenseFile=eula.rtf
But on some machines the EULA windows shows the text as escape codes, not the text itself:
{\rtf1\adeflang1037\ansi\ansicpg1252\uc1\ ...
Even more interesting that I use the same rtf file for several installations. And on one of them the installation shows the rtf EULA as a text and in others as an escape codes on the same machine. The *.iss are the same except installed files.
Is there some way to be sure that my rtf EULA file will be shown without problem on any machine?
A don't want to use plain text since in this case I lose formatting.
Ok, I've found the solution. The rtf file was saved with Word. The file had size 45k and contained tons of waste. After opening and resaving the file with WordPad the size reduced to 10k and now the file contains only relevant tags and text. It looks that Inno Setup just unable to parse Word's monstrous output.
I received files from a client that use a mixture of English and an Arabic alphabet, but upon opening, symbols have replaced the Arabic letters.
I've tried using a couple different word processors, and I've found an answer from Microsoft help center that should solve my problem. http://office.microsoft.com/en-001/word-help/choose-text-encoding-when-you-open-and-save-files-HA010121249.aspx#BM2
However, I get stuck after #4. The instructions say that once you check off the option to "Confirm file format conversion on open", the Conversion dialogue will open automatically when you open a document ... but this is just not happening. I've tried restarting the program.
Does anyone know what is going on?
I have a wordpress installation that clients can edit, all characters display ok. On the main homepage I query the same database for the same title and post content, but it doesn't display correctly - just a question mark
I have tried sending the utf8 headers manually, through htaccess and through meta tags. I have used SET name UTF8 (which turns the characters into the diamond symbol with a questionmark inside).
I genuinely cant figure out what it could be now and I really need these characters to display correctly.
Heres the homepage, you can see in the Sounddhism 6 preview that there are lots of question marks, if you click on it you will see what they are meant to look like
http://nottingham.subverb.net
I have passed it through the validator and it gives me this error:
Sorry, I am unable to validate this document because on line 373 it contained one or more bytes that I cannot interpret as utf-8 (in other words, the bytes found are not valid values in the specified Character Encoding). Please check both the content of the file and the character encoding indication.
The error was: utf8 "\xA0" does not map to Unicode
Which, i appreciate is supposed to help me, but I don't know what to do about it. Especially since that line, the letter generating the error is supposed to be a space and is AFTER the offending question marks.
Can anyone help?
Compare the encoding of both the back-end scripts in Wordpress and also your homepage script. If you're using IE, right-click the page and check the encoding. Sometimes it's set to "Auto-detect" and IE will often detect a different encoding for different pages, causing strange issues like this.
If you're not using IE, try using a tool like Fiddler to see exactly what encoding (and what bytes are being sent back and forth both in the back-end and your homepage script.
If forcing UTF-8 on your homepage script doesn't work, I would guess that the back-end is not using UTF-8.
I see with some apps like Toodledo they use checkmarks for their revision history. How can you show/use special characters in an App Store product description? Does it allow HTML or do you just have to use ascii character codes?
Any tips/tricks for better presentation of our app's product information?
Thank you.
I think Apple just made the rule stricter on the App Store. I have been using special characters in my metadatas for a very long time but got a bad surprise today when trying to submit a new version:
Got this error message on iTunes Connect:
What's New In This Version must not contain the following characters: ★, ❤
Simply enter the characters using the character table in OS X.
To show it, go to OS X System Preferences -> International and select "Show Input Sources in Menu Bar". You should get a flag symbol next to the clock in the menu bar. Clicking on it results in a menu where you can open the character table, in which you can select and paste pretty much any character.
I am the author of the Toodledo app. Here is how I did it. I found the character I wanted on the internet by searching for "unicode symbols". I found it on wikipedia
I then copy and pasted the checkmark ✓ into my app description. And every time I need to make a new checkmark, I go and copy and paste it again since I don't know how to type it. There are lots of interesting symbols to choose from. I also use a star★
UnicodeChecker is an excellent Mac app that contains a database of over 100,000 characters defined in Unicode. You can search for characters by their assigned English names. For example, search for "check" to find several kinds of checkmark characters. Once found, you can copy a character and paste into your description.
UnicodeChecker is free of cost.