Newbe Dev Stack

Answer : Didn't read most of you post, sorry. But just fixing on the final little question what is the ASCII key code for Tab? ASCII value for tab is 9 (decimal or hex), so try Alt + ( Numpad 0 , Numpad 9 ). But, I've just tested doing so in this very edit box and it doesn't work, but it does in notepad, MS Word, etc. I wonder why...? Anyway, if you really need a tab somewhere odd, try copying one from notepad and pasting it where you need it - that's what I tend to do. Edit If you're doing this for it to be displayed on a website (which is what I think you're implying), a tab character may be ignored because HTML tends to ignore whitespace (outside of pre blocks, etc). If it is HTML you could also use the HTML entity version 	 as well, but this will function in the same way. The code is ALT + 0 0 9 However, I don't think it will accomplish what you are after. Hope this helps you -- you have quite a long question :-) Wikipedia ...

Answer : For some reason Blender import doesn't support FBX models that are serialized to text. As a workaround the model can be changed to binary FBX model and imported to Blender. At least I am able to use Autodesk FBX 2013.3 Converter even I don't have any other Autodesk software installed. Other option that might work is to use Bos FBX Importer. PS. If you want to export FBX models from Blender and be able to import them again, you can choose version: FBX 7.4 binary not FBX 6.1 ASCII in the export settings panel. If you have Visual Studio installed try to open the original file then save it and import in Blender. This should work. Unfortunately I can't comment yet but here's an update to maZZZu's answer: The Bos FBX Importer will also not open ASCII .fbx files, however Autodesk's FBX Converter still does. Here's the updated URL: https://www.autodesk.com/developer-network/platform-technologies/fbx-converter-archives

Answer : $ echo AB | perl -lpe '$_=unpack"B*"' 0100000101000010 $ echo 0100000101000010 | perl -lpe '$_=pack"B*",$_' AB -e expression evaluate the given expression as perl code -p : sed mode. The expression is evaluated for each line of input, with the content of the line stored in the $_ variable and printed after the evaluation of the expression . -l : even more like sed : instead of the full line, only the content of the line (that is, without the line delimiter) is in $_ (and a newline is added back on output). So perl -lpe code works like sed code except that it's perl code as opposed to sed code. unpack "B*" works on the $_ variable by default and extracts its content as a bit string walking from the highest bit of the first byte to the lowest bit of the last byte. pack does the reverse of unpack . See perldoc -f pack for details. With spaces: $ echo AB | perl -lpe '$_=join " ", unpack...

Answer : If you want a portable way, then you should use the Unicode code points (which have defined glyphs associated to them): ♠ U+2660 Black Spade Suit ♡ U+2661 White Heart Suit ♢ U+2662 White Diamond Suit ♣ U+2663 Black Club Suit ♤ U+2664 White Spade Suit ♥ U+2665 Black Heart Suit ♦ U+2666 Black Diamond Suit ♧ U+2667 White Club Suit Remember that everything below character 32 in ASCII is a control character . They have a meaning associated with them and you don't have a guarantee of getting a glyph or a behavior there (even though most control characters to have glyphs, although they were never intended to be printable). Still, it's not a safe bet. However, using Unicode needs proper font and encoding support which may or may not be a problem on UNIX-likes. On Windows at least some of the above code points map to the ASCII control character glyphs you're outputting if the console is set to raster fonts (and therefore not supporting Unicode or anything else th...

Answer : In modern times, ASCII is now a subset of UTF-8, not its own scheme. UTF-8 is backwards compatible with ASCII. Yes, except that UTF-8 is an encoding scheme. Other encoding schemes include UTF-16 (with two different byte orders) and UTF-32. (For some confusion, a UTF-16 scheme is called “Unicode” in Microsoft software.) And, to be exact, the American National Standard that defines ASCII specifies a collection of characters and their coding as 7-bit quantities, without specifying a particular transfer encoding in terms of bytes. In the past, it was used in different ways, e.g. so that five ASCII characters were packed into one 36-bit storage unit or so that 8-bit bytes used the extra bytes for checking purposes (parity bit) or for transfer control. But nowadays ASCII is used so that one ASCII character is encoded as one 8-bit byte with the first bit set to zero. This is the de facto standard encoding scheme and implied in a large number of specifications, but strictly s...