Fixed lots of issues with installing a low-caps version of fshell from SIS file. * Fixed issue in CCommandFactory whereby some APIs like GetCommandInfoL could trigger allocations on the wrong heap or signals to the wrong thread. The symptoms were often seen as a crash in the which_00 thread when running ciftest. * Lots of build fixes for when FSHELL_PROTECTED_UIDS isn't defined and when all capabilities aren't available. * Added new platform.mmh macro FSHELL_OPEN_SIGNED. * Open signing of fshell SIS files is now supported for production S60 handsets. Build fshell with the FSHELL_OPEN_SIGNED macro defined (and without defining FSHELL_CAP_ALL or FSHELL_PROTECTED_UIDS) in your platform.mmh and submit \epoc32\fshell\fshell.unsigned.sis to https://www.symbiansigned.com/app/page/public/openSignedOnline.do . The following commands are not available when using Open Signing due to Platform Security restrictions: fdb; kerninfo; chunkinfo; svrinfo; objinfo; sudo; fsck; localdrive; ramdefrag; readmem; reboot; setcritical; setpriority. Others such as chkdeps, e32header, ps, and fshell itself will run but in a restricted capacity (for example, fshell will no longer allow you to modify files in the \sys\bin directory). * Removed commands objinfo, svrinfo, chunkinfo, readmem, fsck completely when memory access isn't present - previously they would still appear in the help but would give an error if you tried to run them.

#!fshell
# fshell-unicode-test.script
# 
# Copyright (c) 2010 Accenture. All rights reserved.
# This component and the accompanying materials are made available
# under the terms of the "Eclipse Public License v1.0"
# which accompanies this distribution, and is available
# at the URL "http://www.eclipse.org/legal/epl-v10.html".
# 
# Initial Contributors:
# Accenture - Initial contribution
#

# Note this file is UTF-8!

# Assume fshell-basic-test is working and this Error definition doesn't need testing
var KEEP_GOING not-defined && export Error 'fshell -e "echo ^"Test failed, env is:^" && env && error"'
var KEEP_GOING defined && export Error 'error -39 "Test failure in $SCRIPT_NAME at line $SCRIPT_LINE"'

export TEST_STRING "EAcute:^u00E9 Beta:^u03b2 Smiley:^u263a"
echo -n EAcute:é Beta:β Smiley:☺ | export -s RESULT

# Check symmetric properties - I don't imagine these will ever fail unless variable expansion is really broken
var TEST_STRING == "$TEST_STRING" || $Error
var RESULT == "$RESULT" || $Error

var RESULT == "$TEST_STRING" || $Error
# And vice-versa
var TEST_STRING == "$RESULT" || $Error

echo "$TEST_STRING" > unicodetest.txt # This will output in UTF-8

cat --encoding ltk-utf-8 unicodetest.txt | export -s CATRESULT
var CATRESULT == "$TEST_STRING^r^n" || $Error

export -s REDIRRESULT < unicodetest.txt
var REDIRRESULT == "$TEST_STRING^r^n" || $Error

rm unicodetest.txt