ISO/IEC 8859-1 File

Hi
I have a file that is fomatted using the ISO/IEC 8859-1 format.
I would like to load this file into a table in the database and want to convert the file contents into readable letters etc.
Can you let me know what is best way to approach this problem
Thanks
Brendan
Edited by: Brendan on Jun 16, 2010 2:13 PM

ISO/IEC 8859-1 is called WE8ISO8859P1 in Oracle,
Assuming your database NLS_CHARACTERSET defines all characters known in WE8ISO8859P1 (= it is WE8MSWIN1252, WE8ISO8859P1 or UTF8/AL32UTF8)
then you can simply use external table or sqlldlr to read the .txt file.
in the externall table or sqlldr syntax/control file use then CHARACTERSET=WE8ISO8859P1 and Oracle will do the conversion
See also on MOS Note:227330.1 Character Sets & Conversion - Frequently Asked Questions
18. What is the best way to load non-US7ASCII characters using SQL*Loader or External Tables?
Note that I'm a bit sceptic that a file will be ISO/IEC 8859-1 / WE8ISO8859P1, most data is coming from windows clients and in that case the data in very likely in the WE8MSWIN1252 characterset . (if the file contain any of these characters €‚ƒ„…†‡ˆ‰Š‹ŒŽ‘’“”•–—˜™š›œžŸ then it's very likely 1252)
Use Sqldeveloper to check the result to avoid problems with wrong configure clients.
Gunther

Similar Messages

What is the default file format for saving in MS Office 2013? Is it still the transitional OOXML or the ISO/IEC 29500 strict format?

As I have read, MS Office 2013 is able to read and write the ISO/IEC 29500 strict (standardized Office Open XML) file format. MS Office 2010 was only able to read the strict format and MS Office 2007 could neither read nor write the strict format. The
.docx, .xlsx and .pptx saved by Office 2007 and 2010 were only complying to the OOXML transitional, as far as I understood.
My main question is what the default file format for saving in MS Office 2013 actually is? Is it still the transitional OOXML or the ISO/IEC 29500 strict format?
In case, MS Office still saves in the transitional standard by default, is it possible to set the strict standard in the settings? Is this recommended (I assume that OOXML strict is the future) to do this?
Thanks.

Yes, the Transitional is still the default file format for saving in Office 2013, and we can modify this setting in Word Options, Save:
As Alex Brown covers in his
blog post, "Transitional is intended to preserve the fidelity of existing binary documents being migrated to ISO/IEC 29500, and includes many legacy features for compatibility with existing documents. Strict is a subset of Transitional that does not
include legacy features – this makes it theoretically easier for a new implementer to support (since it has a smaller technical footprint, so to speak), but also makes it less able to preserve the fidelity of existing documents."
Max Meng
TechNet Community Support

What about ISO/IEC-7816 file structure, Is this concept is not in jcard.

Hello all,
I read out ISO/IEC 7816-4 and it tell about MF , DF, EF files which are used in smart card, i am using java card.
I am reading java card but i did not read about these file structure,
according to iso/iec-7816-4 , A4 is a INS for SELECT FILE command. In scosta if i want to save name in smart card then i do
*1*- create MF
*2*-create Df ( INS- E0)
*3*- create ef with record oriented structure(INS-E0)
*4* run write record command (*INS-D2*)
and now i can read this name whenever i want by using read record command.
I only want to know that if i want to record several names in java card (in java card eeprom ) then which line i need to write inside the PROCESS () method of applet.
-----------how i permanent save in smart card memory?
-----------how i read the data from perticular location or the location where name exist?
Thanks in advance..............
Edited by: rohit pathak on Feb 9, 2012 10:41 PM
Edited by: rohit pathak on Feb 9, 2012 10:42 PM

if (selectingApplet())
               return;
// this method is use to make a difference between select applet
//apdu { have to call it before any apdu pass to card, this apdu is isolate to process method }
//and other apdu { here class and INS is for your choice,
// it depends how u implement it in process().amazing Umer, atleast for me really it's gr8 to have you here..
you know i am a beginner so it is sure that there would be a no. of question in my mind now!!!!!and I want to share with you for your answer as well try to get it by my own, u already help me a lot , and i would
be always thankful for this. I am posting some questions here, if you feel it is genuine question , pls reply and if
you think i am bothering you to ask such a foolish question , u dont!!!!
QUESTION -1
As I know about architecture of any application is -
                //normal java software                          java card                                  java card
                  // 1                                               2                                      3
1-            application program                        host application                           host application
2-                     JVM                                   Applets                                       Applets
3-              operating system                JCRE(which contain all classes, JVM ....)                 JCRE(act as a O.S too)
4                    hardware                              Operating system                                 H/W
5                                                                        hardwareWhat do u think- case 2 is right? or 3 is!!!!!!!!!!!
I think - case 3 is right!!!!
As i study from several sources , JCRE is complete package - it behaves as a operation system and use the functionality of component it contain. I also think if i will purchase a java card from any vendor , it would have JCRE inside it (means everthing inside it,), i only need to develop the applet according to my requirement and install it by on card installer program
QUESTION 2- what is the advantage of java card.?
// I think.
as i read out , i got the line that it is platform independent and support multiple application. applicaton point of
view , I am agree but how it is platfrom independent. if we use java card for smart card development, then
i will purchase Java card from differnt vendor , all will provide me card with supported jcre inside it, so why
this is advantage here?
// in case of window based application , it really make sense because if i will make any window application with java
// i can run it in windows , linux , unix and most of os flavours, here i can see the beauty of java language.
Clear me this and add some other java card advantages, which make java card goodquestion 3-
Now I am capaple to make simple applets, so I want to check the entire java card process atleast once before
going in deep of something, I am thinking to implement prepaid card concept , i made it applet for it ,it will
contain a page with 2 text box ( 1- for recharge 2- for money deduction ) and two button , with button click i
want to select the applet and want to pass the apdu.
( a) how i can make host window application ? (i think awt will work for me? , *
i never make any java window application yet) *
( b) still i dont have any java card , i want to make it by using simulator, is it possible?
(c) in this scenario what framework i need to study Ex. Import javacard.framework.* for making
applet or from where i need to start.regards:
rohit pathak
Edited by: rohit pathak on Feb 9, 2012 10:39 PM

Any class who do == ISO ISO/IEC 9797-1 padding 2 algorithm 3

Hi all,
Working on java cards, I need to crypt a bytes array using a 3DES key like :
MAC = RetailMAC [S'] <Kmac>
- S' is the array
- Kmac is the 3DES key
- MAC is the result
(this is what I have in my spec).
The only information I have about RetailMAC is ISO ISO/IEC 9797-1 padding 2 algorithm 3.
Unfortunately, I don't have this ISO...
I'm looking for a class with method (in JAVA) which implement this algo.
I found this but don't know if it is correct or not :
cipherCBC = Cipher.getInstance(Cipher.ALG_DES_CBC_ISO9797_M2, false);but I don't know if "ALG_DES_CBC_ISO9797_M2" is the correct argument.
[javadoc of cipher class |http://www.informatik.uni-augsburg.de/swt/lehre/javacard/JavaCard-2.1-API/javacardx.crypto.Cipher.html#ALG_DES_ECB_ISO9797_M2]
Any help is welcome !
Gilloull

The code I am trying to build is an applet which will interact with my card.
As a terminal, I have to crypt an array bytes with MacRetail and the program on my card has to decrypt it and compare it with other datas.
I don't have access to the card program.
this is my code for testing :
byte[] buf = apdu.getBuffer();
byte[] data = {(byte)0x72,(byte)0xC2,(byte)0x9C,(byte)0x23,(byte)0x71,(byte)0xCC,(byte)0x9B,(byte)0xDB,
             (byte)0x65,(byte)0xB7,(byte)0x79,(byte)0xB8,(byte)0xE8,(byte)0xD3,(byte)0x7B,(byte)0x29,
          (byte)0xEC,(byte)0xC1,(byte)0x54,(byte)0xAA,(byte)0x56,(byte)0xA8,(byte)0x79,(byte)0x9F,
          (byte)0xAE,(byte)0x2F,(byte)0x49,(byte)0x8F,(byte)0x76,(byte)0xED,(byte)0x92,(byte)0xF2};
byte[] key = {(byte)0x79,(byte)0x62,(byte)0xD9,(byte)0xEC,(byte)0xE0,(byte)0x3D,(byte)0x1A,(byte)0xCD,
             (byte)0x4C,(byte)0x76,(byte)0x08,(byte)0x9D,(byte)0xCE,(byte)0x13,(byte)0x15,(byte)0x43};
byte[] correctResult = {(byte)0x5F,(byte)0x14,(byte)0x48,(byte)0xEE,(byte)0xA8,(byte)0xAD,(byte)0x90,(byte)0xA7};
byte[] okay = {(byte)0xFF,(byte)0xFF,(byte)0xFF,(byte)0xFF};
DESEngine des = new DESEngine();
ISO9797Alg3Mac mac = new ISO9797Alg3Mac(des);
mac.init(new DESedeParameters(key));
byte[] result = new byte[mac.getMacSize()];
mac.update(data, (short)0, (short)data.length);
mac.doFinal(result, 0);
if (Util.arrayCompare(result, (short)0, correctResult, (short)0, (short)8) == (byte)0x00)
     Util.arrayCopyNonAtomic(okay, (short) 0, buf, (short)0, (short)4);
     apdu.setOutgoingAndSend((short)0, (short)4);
else
     ISOException.throwIt(ISO7816.SW_DATA_INVALID);
}I got the correctResult / Data / key from this post : Link
now, in Eclipse, the error I have next to my package declaration at the top of my program is :
Resolving constant-pool of clazz Lpck/gemalto/Gemalto; failed : missing export file for package org/bouncycastle/crypto/engines
this are all the packages I am importing :
import org.bouncycastle.crypto.BlockCipher;
import org.bouncycastle.crypto.CipherParameters;
import org.bouncycastle.crypto.Mac;
import org.bouncycastle.crypto.engines.DESEngine;
import org.bouncycastle.crypto.macs.ISO9797Alg3Mac;
import org.bouncycastle.crypto.modes.CBCBlockCipher;
import org.bouncycastle.crypto.params.DESParameters;
import org.bouncycastle.crypto.params.DESedeParameters;
import org.bouncycastle.crypto.params.KeyParameter;
import javacard.framework.APDU;
import javacard.framework.Applet;
import javacard.framework.ISO7816;
import javacard.framework.ISOException;
import javacard.framework.Util;
import javacard.security.CryptoException;
import javacard.security.DESKey;
import javacard.security.KeyBuilder;
import javacard.security.RandomData;
import javacardx.crypto.Cipher;I don't understand the error because I downloaded the library from the official website, and the package is correctly imported (And Eclipse notifies when a package is not imported).

Read QR Code not found ISO/IEC 15415

Please can anyone advise me, how setting IMAQ Read QR code, so that I read QR code ISO/IEC 15415??? Android phone read QR code not problem, but I need learn read this code with help IMAQ Read QR code or other tool in labview, but I don't know what tool???

Typically the error presented by labview arises when you try do some operation on an image type that is inappropriate for the operation.
image types are:
RGB 32
RGB 64
U8
I8
U16
I16
etc...
and refers to the datatype used for a pixel
when rotating you typically supply a destination image, and my guess is that the dst image is of a different type than what is rotated...
hence the output of the rotation is now of the dst image type, instead of the input type.
to avoid this, when creating the dst image, use the "get image info" to get the type of the input image, and then wire that to the "create image"
Engineer, M.Sc. Autonomous Systems, Automation and Control of non-linear systems
Project Engineer @ R&D A/S
www.rdas.dk

Convert file encoding from ASMO-708 to Unicode

Hi,
I have txt files from a dos application. the files in ASMO-708/ISO-8859-6 encoding
i did a test program to see if i will be able to see the characters in Unicod(eclips-debug)
i read the file using
Reader r = new BufferedReader(new InputStreamReader(txtfile ,"ISO-8859-6"));i did this on text file, what i found that i could read some characters and some not.
like character in asmo-708 is 0x99 should correspond to 0x0622(unicode)
but it respond to 0x3f which is undefined character.
my question is why some characters work and some not?
Thanks

Likewise Wikipedia, whose article about ISO-8859-6 says
"Code values 0x00�0x1F, 0x7F, 0x80�0x9F, 0xA1�0xA3, 0xA5�0xAB, 0xB0�0xBA, 0xBC�0xBE, 0xC0, 0xDC�0xDF, and 0xF3�0xFF are not assigned to characters by ISO/IEC 8859-6."

MORX and GSUB shaping in HTML

Question: There is talk of supporting implementations of the intelligent composition model in HTML. Opera is talking of supporting some optional GSUB shaping tags and Safari supports the obligatory CMAP shaping tag so the audience will see the stylistics the author sees. OS X 10.5 Server, and Freeway as well, seem to be moving into this direction. Does anyone have comment or criticism of what at first sight seems to be the beginnings of a technical trend?
Issue: The intelligent composition model was iniated at WWDC 1989 and introduced at Seybold in September 1989 as TrueType. The idea is to separate processing of semantic character information from processing of stylistic glyph information in order to shield the public character set from insertion of incorrect public character information which is the consequence of one-to-one mapping models.
Hitherto, only page description models have supported the optional shaping tables in the SFNT Spline Font file format architecture, but the reality is that this does not work well. The Apple Portable Digital Document format supported the glyph stream but not the character stream and the Adobe Portable Document Format does not support the character stream when PS/EPS is intermediary.
Page markup models have had no support for preserving fixed appearance, not even the fixed appearance defined by the obligatory CMAP shaping. CMAP shaping is sufficient for informal Latin typography, but it is neither sufficient for formal Latin typography nor for informal and formal Arabic and Indic typography.
In other words, if page markup models support not only the character stream but the shaping that is necessary for formal Latin and informal non-Latin typography, the problems posed by page description models would be overcome. There are also other problems that would be overcome, since ISO-IEC 10646 is not problem-free in and of itself.
ISO-IEC 10646 supports private character information on Level 1, Level 2 and Level 3. ISO-IEC 10646 also supports private permutations of public characters (known in ISO 15076 as 'pre-evaluated transforms'). These private permutations have no public synonyms for searching and they appear to the audience as generative algorithmic graphemes.
Ideally, the point of coding text is to match the meaning and the point of composing type is to match the mark. ISO-IEC 10646 permits authors to mix these modes and attempt to hardcode appearance into the plain text. In this case the plain text is unsearchable, a problem which providing support for shaping in page markup models would also solve.
If page markup models evolve to support shaping, then there is no reason to try to hardcode shaping into plain text, and the risk of private information in publishing is reduced.
Best wishes,
Henrik Holmegaard
technical writer, mag.scient.soc.
References:
http://www.mactech.com/articles/mactech/Vol.05/05.10/Typography/index.html
http://unicode.org/mail-arch/unicode-ml/y2008-m02/0043.html
http://www.mail-archive.com/[email protected]/msg12126.html

OK, everybody publishes in ISO-IEC 8859-1:1987 for the Anglo-American world and Western Europe as it was before the fall of the Iron Curtain? No Greek, no Cyrillic, not even Slavonic in the Latin script? So, no problem with Private Use Area charactoids and Combining Diacritic charactoids in comprehensive content cataloguing since these two categories are not possible in ISO-IEC 8859-1:1987.
Well, well ... there is a wider world.
Best,
Henrik

Query with ctype facet results

Hi,
Before I ask my question, let me give you a summary of my development environment. I am using Solaris 10 U4 on an x86 virtual machine and applied any locale related patches. I have also installed Sun Studio 12 and applied any C++ related patches. I currently have my locale set to en_AU.ISO8859-1.
I have a test program which displays the character classifications of all 256 characters in the 8859-1 codeset. This test program is as follows:
#include <locale>
#include <iostream>
#include <iomanip>
using namespace std;
int main()
     const locale &rLocale = locale("");
     const ctype<char> &rCtype = use_facet<ctype<char> >(rLocale, 0);
     for (unsigned vI = 0; vI < 256; ++vI)
          unsigned char vChar = static_cast<unsigned char>(vI);
          cout
               << "0x"
               << hex << setiosflags(ios_base::internal | ios_base::uppercase) << setfill('0')
               << setw(2) << static_cast<unsigned>(vChar)
               << dec << resetiosflags(ios_base::internal | ios_base::uppercase) << setfill(' ')
               << " : "
               << (rCtype.is(ctype_base::space, vChar) ? "space" : ".....")
               << " "
               << (rCtype.is(ctype_base::print, vChar) ? "print" : ".....")
               << " "
               << (rCtype.is(ctype_base::cntrl, vChar) ? "cntrl" : ".....")
               << " "
               << (rCtype.is(ctype_base::upper, vChar) ? "upper" : ".....")
               << " "
               << (rCtype.is(ctype_base::lower, vChar) ? "lower" : ".....")
               << " "
               << (rCtype.is(ctype_base::alpha, vChar) ? "alpha" : ".....")
               << " "
               << (rCtype.is(ctype_base::digit, vChar) ? "digit" : ".....")
               << " "
               << (rCtype.is(ctype_base::punct, vChar) ? "punct" : ".....")
               << " "
               << (rCtype.is(ctype_base::xdigit, vChar) ? "xdigit" : "......")
               << endl;
     return 0;
}When I run this test program, I am expecting all 256 characters to be classified according to ISO/IEC 6429:1992 and ISO/IEC 8859-1:1998. However, what I am getting is as follows:
{result}
0x00 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x01 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x02 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x03 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x04 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x05 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x06 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x07 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x08 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x09 : space ..... cntrl ..... ..... ..... ..... ..... ......
0x0A : space ..... cntrl ..... ..... ..... ..... ..... ......
0x0B : space ..... cntrl ..... ..... ..... ..... ..... ......
0x0C : space ..... cntrl ..... ..... ..... ..... ..... ......
0x0D : space ..... cntrl ..... ..... ..... ..... ..... ......
0x0E : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x0F : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x10 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x11 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x12 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x13 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x14 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x15 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x16 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x17 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x18 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x19 : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x1A : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x1B : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x1C : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x1D : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x1E : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x1F : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x20 : space print ..... ..... ..... ..... ..... ..... ......
0x21 : ..... print ..... ..... ..... ..... ..... punct ......
0x22 : ..... print ..... ..... ..... ..... ..... punct ......
0x23 : ..... print ..... ..... ..... ..... ..... punct ......
0x24 : ..... print ..... ..... ..... ..... ..... punct ......
0x25 : ..... print ..... ..... ..... ..... ..... punct ......
0x26 : ..... print ..... ..... ..... ..... ..... punct ......
0x27 : ..... print ..... ..... ..... ..... ..... punct ......
0x28 : ..... print ..... ..... ..... ..... ..... punct ......
0x29 : ..... print ..... ..... ..... ..... ..... punct ......
0x2A : ..... print ..... ..... ..... ..... ..... punct ......
0x2B : ..... print ..... ..... ..... ..... ..... punct ......
0x2C : ..... print ..... ..... ..... ..... ..... punct ......
0x2D : ..... print ..... ..... ..... ..... ..... punct ......
0x2E : ..... print ..... ..... ..... ..... ..... punct ......
0x2F : ..... print ..... ..... ..... ..... ..... punct ......
0x30 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x31 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x32 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x33 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x34 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x35 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x36 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x37 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x38 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x39 : ..... print ..... ..... ..... ..... digit ..... xdigit
0x3A : ..... print ..... ..... ..... ..... ..... punct ......
0x3B : ..... print ..... ..... ..... ..... ..... punct ......
0x3C : ..... print ..... ..... ..... ..... ..... punct ......
0x3D : ..... print ..... ..... ..... ..... ..... punct ......
0x3E : ..... print ..... ..... ..... ..... ..... punct ......
0x3F : ..... print ..... ..... ..... ..... ..... punct ......
0x40 : ..... print ..... ..... ..... ..... ..... punct ......
0x41 : ..... print ..... upper ..... alpha ..... ..... xdigit
0x42 : ..... print ..... upper ..... alpha ..... ..... xdigit
0x43 : ..... print ..... upper ..... alpha ..... ..... xdigit
0x44 : ..... print ..... upper ..... alpha ..... ..... xdigit
0x45 : ..... print ..... upper ..... alpha ..... ..... xdigit
0x46 : ..... print ..... upper ..... alpha ..... ..... xdigit
0x47 : ..... print ..... upper ..... alpha ..... ..... ......
0x48 : ..... print ..... upper ..... alpha ..... ..... ......
0x49 : ..... print ..... upper ..... alpha ..... ..... ......
0x4A : ..... print ..... upper ..... alpha ..... ..... ......
0x4B : ..... print ..... upper ..... alpha ..... ..... ......
0x4C : ..... print ..... upper ..... alpha ..... ..... ......
0x4D : ..... print ..... upper ..... alpha ..... ..... ......
0x4E : ..... print ..... upper ..... alpha ..... ..... ......
0x4F : ..... print ..... upper ..... alpha ..... ..... ......
0x50 : ..... print ..... upper ..... alpha ..... ..... ......
0x51 : ..... print ..... upper ..... alpha ..... ..... ......
0x52 : ..... print ..... upper ..... alpha ..... ..... ......
0x53 : ..... print ..... upper ..... alpha ..... ..... ......
0x54 : ..... print ..... upper ..... alpha ..... ..... ......
0x55 : ..... print ..... upper ..... alpha ..... ..... ......
0x56 : ..... print ..... upper ..... alpha ..... ..... ......
0x57 : ..... print ..... upper ..... alpha ..... ..... ......
0x58 : ..... print ..... upper ..... alpha ..... ..... ......
0x59 : ..... print ..... upper ..... alpha ..... ..... ......
0x5A : ..... print ..... upper ..... alpha ..... ..... ......
0x5B : ..... print ..... ..... ..... ..... ..... punct ......
0x5C : ..... print ..... ..... ..... ..... ..... punct ......
0x5D : ..... print ..... ..... ..... ..... ..... punct ......
0x5E : ..... print ..... ..... ..... ..... ..... punct ......
0x5F : ..... print ..... ..... ..... ..... ..... punct ......
0x60 : ..... print ..... ..... ..... ..... ..... punct ......
0x61 : ..... print ..... ..... lower alpha ..... ..... xdigit
0x62 : ..... print ..... ..... lower alpha ..... ..... xdigit
0x63 : ..... print ..... ..... lower alpha ..... ..... xdigit
0x64 : ..... print ..... ..... lower alpha ..... ..... xdigit
0x65 : ..... print ..... ..... lower alpha ..... ..... xdigit
0x66 : ..... print ..... ..... lower alpha ..... ..... xdigit
0x67 : ..... print ..... ..... lower alpha ..... ..... ......
0x68 : ..... print ..... ..... lower alpha ..... ..... ......
0x69 : ..... print ..... ..... lower alpha ..... ..... ......
0x6A : ..... print ..... ..... lower alpha ..... ..... ......
0x6B : ..... print ..... ..... lower alpha ..... ..... ......
0x6C : ..... print ..... ..... lower alpha ..... ..... ......
0x6D : ..... print ..... ..... lower alpha ..... ..... ......
0x6E : ..... print ..... ..... lower alpha ..... ..... ......
0x6F : ..... print ..... ..... lower alpha ..... ..... ......
0x70 : ..... print ..... ..... lower alpha ..... ..... ......
0x71 : ..... print ..... ..... lower alpha ..... ..... ......
0x72 : ..... print ..... ..... lower alpha ..... ..... ......
0x73 : ..... print ..... ..... lower alpha ..... ..... ......
0x74 : ..... print ..... ..... lower alpha ..... ..... ......
0x75 : ..... print ..... ..... lower alpha ..... ..... ......
0x76 : ..... print ..... ..... lower alpha ..... ..... ......
0x77 : ..... print ..... ..... lower alpha ..... ..... ......
0x78 : ..... print ..... ..... lower alpha ..... ..... ......
0x79 : ..... print ..... ..... lower alpha ..... ..... ......
0x7A : ..... print ..... ..... lower alpha ..... ..... ......
0x7B : ..... print ..... ..... ..... ..... ..... punct ......
0x7C : ..... print ..... ..... ..... ..... ..... punct ......
0x7D : ..... print ..... ..... ..... ..... ..... punct ......
0x7E : ..... print ..... ..... ..... ..... ..... punct ......
0x7F : ..... ..... cntrl ..... ..... ..... ..... ..... ......
0x80 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x81 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x82 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x83 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x84 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x85 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x86 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x87 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x88 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x89 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x8A : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x8B : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x8C : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x8D : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x8E : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x8F : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x90 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x91 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x92 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x93 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x94 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x95 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x96 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x97 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x98 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x99 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x9A : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x9B : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x9C : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x9D : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x9E : ..... ..... ..... ..... ..... ..... ..... ..... ......
0x9F : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA0 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA1 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA2 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA3 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA4 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA5 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA6 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA7 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA8 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xA9 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xAA : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xAB : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xAC : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xAD : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xAE : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xAF : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB0 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB1 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB2 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB3 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB4 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB5 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB6 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB7 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB8 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xB9 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xBA : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xBB : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xBC : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xBD : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xBE : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xBF : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC0 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC1 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC2 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC3 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC4 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC5 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC6 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC7 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC8 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xC9 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xCA : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xCB : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xCC : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xCD : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xCE : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xCF : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD0 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD1 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD2 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD3 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD4 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD5 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD6 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD7 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD8 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xD9 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xDA : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xDB : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xDC : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xDD : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xDE : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xDF : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE0 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE1 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE2 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE3 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE4 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE5 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE6 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE7 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE8 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xE9 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xEA : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xEB : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xEC : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xED : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xEE : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xEF : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF0 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF1 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF2 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF3 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF4 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF5 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF6 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF7 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF8 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xF9 : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xFA : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xFB : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xFC : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xFD : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xFE : ..... ..... ..... ..... ..... ..... ..... ..... ......
0xFF : ..... ..... ..... ..... ..... ..... ..... ..... ......
{result}
Notice that the lower 128 characters have the correct classification but the upper 128 characters do not have any classification information. Am I missing something here or is the system not behaving correctly? Is there a fix for this problem?
Regards,
Leo

It looks like we have a problem with locale("") not setting the environment for the program.
If you use
const locale &rLocale = locale("en_AU.ISO8859-1"); the code works as you expect.
Please file a bug report at http://bugs.sun.com

Does Adove FrameMaker 7.0 support Thai language?

Hello,
after creating a sample document with some Thai text, I save it as MIF 7.0 . There is a prompt saying that saving in this format will cause loss of information related to new features. Then, after reopening the file in FrameMaker instead of Thai characters i get question marks.
I'm using Adobe FrameMaker v10 , Thai Kedmanee keyboards, my text is written using font that supports Thai characters (Angsana New) .
So, ladies and gentlemen - is there anything i can do with this or FrameMaker 7.0 just does not support Thai language?
Thanks in advance,
Chris

Your Angsana New is likely a Unicode font. When you type Thai characters in it, what goes into the document is 3-byte UTF8 from the U+0E00 codepoint block. These are completely different binary values vs. the 8-bit code page 874 legacy encoding for Thai overlay fonts, and may not even have the same ordering of glyphs in the block.
You're going to need a legacy 8-bit Thai font, possibly Angsana code page 874, and you'll need to know the mapping. On Windows, you'll might even have to type them as Alt sequences, based on the {128-255 decimal?) values of the code points. Alternatively, Windows will have a keyboard mapping for code page 874.
ISO/IEC 8859-11:2001, code page 874 is apparently not the same as TIS-620, if that matters.
Now entering the Unicode parking lot.
Do not back up.
Severe text damage may result.

Text Substitution: using subscript.

I'd like to set up some automatic text substitutions for chemical compounds, with correct subscript (i.e O2, H2O, CO2 etc).
Text formatting doesn't seem to work in the automatic corrections pane.
This seems like a fairly simple request; is there something I'm missing?
Thanks!

Instead you must insert the Unicode subscript characters from the Character Palette (assuming the ones you need are available).
Below the matrix for superscripts. As a rule, shaping should not be hardcoded (directly drawn) in character space but softcoded (indirectly drawn) in glyph space.
For all superscript numbers the Character Info > Related Characters window reports that NFD, NFC, NFKD and NFKC are related.
For all superscript numbers Apple TextEdit and Apple Pages do not consider NFD/NFC related to NFKD/NFKC for content-based searching.
For all superscript numbers, it is not possible to predict which search systems will set a synonym for NFKD/NFKC searching.
For superscript numbers one, two, and three there are commonly glyph codes for dedicated glyph designs in TrueType 1:1990 (because these character codes are included in ISO-IEC 8859-1:1987).
For superscript numbers four, five, six, seven, eight, nine and zero there are commonly no glyph codes for dedicated glyph designs in TrueType simple.
Therefore, the rendering system takes the baseline glyph design, scales it down, lifts it up, and remaps the glyph code to the superscript character code.
For the purpose of searching, it would be significantly better if Apple get support for smart shaping into PDF, since shaping superscript glyphs with superscript characters introduces a complexity in searching.
It would also be significantly better for the everyday enduser, if Apple introduced a correction to the Related Characters window that showed standard universal synonyms.
Anything that is not a synonym across all four normalisations should be shown, since trying to do shaping in character space instead of in glyph space (where shaping belongs) is at risk in the current interface.
Which was what I was trying to say at the start of 2008 -:).
Superscript one : NFD ¹, NFC ¹, NFKD 1, NFKC 1
Superscript two : NFD ², NFC ², NFKD 2, NFKC 2
Superscript three : NFD ³, NFC ³, NFKD 3, NFKC 3
Superscript four : NFD ⁴, NFC ⁴, NFKD 4, NFKC 4
Superscript five : NFD ⁵, NFC ⁵, NFKD 5, NFKC 5
Superscript six : NFD ⁶, NFC ⁶, NFKD 6, NFKC 6
Superscript seven : NFD ⁷, NFC ⁷, NFKD 8, NFKC 8
Superscript eight : NFD ⁸, NFC ⁸, NFKD 8, NFKC 8
Superscript nine : NFD ⁹, NFC ⁹, NFKD 9, NFKC 9
Superscript zero : NFD ⁰, NFC ⁰, NFKD 0, NFKC 0

Character set conversion UTF-8 -- ISO-8859-1 generates question mark (?)

I'm trying to convert an XML-file in UTF-8 format to another file with character set ISO-8859-1.
My problem is that the ISO-8859-1 file generates a question mark (?) and puts it as a prefix in the file.
?<?xml version="1.0" encoding="UTF-8"?>
<ns0:messagetype xmlns:ns0="urn:olof">
<underkat>testv��rde</underkat>
</ns0:messagetype>
Is there a way to do the conversion without getting the question mark?
My code looks as follows:
public class ConvertEncoding {
     public static void main(String[] args) {
          String from = "UTF-8", to = "ISO-8859-1";
          String infile = "C:\\temp\\infile.xml", outfile = "C:\\temp\\outfile.xml";
          try {
               convert(infile, outfile, from, to);
          } catch (Exception e) {
               System.out.println(e.getMessage());
               System.exit(1);
     private static void convert(String infile, String outfile,
                                        String from, String to)
                         throws IOException, UnsupportedEncodingException
          //Set up byte streams
          InputStream in = null;
          OutputStream out = null;
          if(infile != null) {
               in = new FileInputStream(infile);
          if(outfile != null) {
               out = new FileOutputStream(outfile);
          //Set up character streams
          Reader r = new BufferedReader(new InputStreamReader(in, from));
          Writer w = new BufferedWriter(new OutputStreamWriter(out, to));
          /*Copy characters from input to output.
           * The InputSreamreader converts
           * from Unicode to the output encoding.
           * Characters that cannot be represented in
           * the output encoding are output as '?'
          char[] buffer = new char[4096];
          int len;
          while((len = r.read(buffer))!= -1) { //Read a block of output
               w.write(buffer, 0, len);
          r.close();
          w.flush();
          w.close();
}

Yes the next character is the '<'
The file that I read from is generated by an integration platform. I send a plain file to it (supposedly in UTF-8 encoding) and it returns another file (in between I call my java class that converts the characterset from UTF-8 to ISO-8859-1). The file that I get back contains the '��' if the conversion doesn't work and '?' if the conversion worked.
My solution so far is to skip the first "junk-characters" when reading from the inputstream. Something like:
private static final char UTF_BOM = '\uFEFF'; //UTF-BOM = ?
String from = "UTF-8", to = "ISO-8859-1";
if (from != null && from.toLowerCase().startsWith("utf-")) { //Are we reading an UTF encoded file?
/*Read first character of the UTF-Encoded file
It will return '?' in the first position if we are dealing with UTF encoding If ? is returned we skip this character in the read
try {
r.mark(1); //Only allow to read one char for the reset function to work
char c;
int i = r.read();
c = (char) i;
if (String.valueOf(UTF_BOM).equalsIgnoreCase(String.valueOf(c))) {
r.reset(); //reset to start position
r.skip(1); //Skip first character when reading from the stream
else {
r.reset();
} catch (IOException e) {
e.getMessage();
//return null;
}

2008.12 archboot test iso/img files

Hi Arch community,
Arch Linux (archboot creation tool) 2008.12-1, "Nepal" has been released.
http://downloads.archlinux.de/iso/archboot/2008.12/
(Thanks Pierre for hosting them in the meanwhile )
This is a test run for the created files, please try to find showstoppers.
If everything is alright, those files can be moved to the mirrors and torrents can be created.
To avoid confusion, this is not an official arch linux release!
It's an installation environment created with the archboot tools.
Please report all bugs only to my email address.
Thanks for testing.
Have Fun
greetings
tpowa
Changelog:
GENERAL:
- kernel 2.6.27.7 usage
- pacman 3.2.1 usage
- RAM recommendations:
* arch or arch64 boot image
160 MB RAM i686/x86_64 (all packages selected, with swap partition)
* lowmem or lowmem64 boot image
64 MB RAM i686/x86_64 (all packages selected, with swap partition)
FIXES:
- merged in setup changes from installer.git
- merged in documentation changes from installer.git
- changed bootmessages
- changed intel wireless hook to improve boot speed
- fixed quickinst
- added new tz script for setting date, time and zones
- added some fixes to km
- added setup startup on first login
- added km and tz to setup dialogs
- added dmraid dialog for mkinitcpio setup
- added ntp to arch and arch64 install environment
KNOWN ISSUES:
- None
ISO and USB image files are provided, which include
i686 and x86_64 core repository. Please check md5sums before using them.
ISO files are standard CD-burnable images.
- Can be burned to CD(RW) media using most CD-burning utilities.
IMG files are full raw disk images.
- Intended for use with USB thumb drives.
- Can be raw-written to a drive using 'dd' or similar utilities.
Further documentation can be found on-disk and on the wiki.
Have fun!
greetings
tpowa

Tobias, you may have read on arch-general that I've been working on a totally refactored installer (installation framework).
It's called AIF. Basically I've taken the old /arch/setup from installer.git and totally refactored everything to make the codebase clean, modular and reusable. Lately I've also been rewriting the whole blockdevice/filesystem part of the installer because it wasn't very good. For more info I refer to http://dieter.plaetinck.be/AIF_the_bran … _Framework , http://archlinux.org/pipermail/arch-gen … 02541.html (albeit most of the info there is a bit outdated now) and http://github.com/Dieterbe/aif/tree/master
I also maintain packages in aur ( http://aur.archlinux.org/packages.php?ID=21565 follows the master branch, where I pull in all the stabilized code, so I recommend this package)
Right now AIF is mostly good for developers/power users who wish to make custom installation procedures.
Towards the reglar user there isn't that much of a difference: the installer looks very similar. although under the hood 95% of the things are different. Right now I'm also working on supporting lvm/dm_crypt.
Anyway, if you're interested, I suggest you take a look at the code and if you like it you could maybe integrate AIF as an alternative, experimental installer. (it doesn't conflict with the other installer, it installs alongside)
Last edited by Dieter@be (2008-12-11 10:27:18)

Bulid Project To IMAGE iso no audio in the final file

Hi
I build project to DVD image (8.54 dual layer, layer break:automatic, format:iso) in the final file "name.iso" I mount to deamon tools and play in PowerDVD i see video but no hear audio
please any ideas

Does your version of PowerDVD support Dolby Digital (AC3) audio?

K8N (MS7220&MS7125) ISO with bios files for flashing from cdrom

============================================================================================
MS7220
============================================================================================
I made a bootable cdrom ISO with different bios files for easy flashing of Diamond Plus
without the need of a floppy drive.
Nothing modded , just collection of MS-7220 Diamond Plus bioses on one bootable cd for conveniance.
Burn ISO (unzip first) and reboot PC with CDROM as 1'st boot device.
A menu tells what to key:
1,2,3,4,5,6 or 7 followed by enter.
Menu looks like this :
+--------------------------------------+
Press 1,2,3,4,5,6,7 followed by enter
to flash with desired version
+--------------------------------------+
1 = MS-7220 bios 1.0
2 = MS-7220 bios 1.1
3 = MS-7220 bios 1.2
4 = MS-7220 bios 1.22
5 = MS-7220 bios 1.33
6 = MS-7220 bios 3.09
7 = MS-7220 bios 3.0A
R:\>
Pressing 1 will flash with following command
afud408 a7220nms.100 /P /B /N /C
Pressing 2 will flash with following command
afud408 a7220nms.110 /P /B /N /C
Pressing 3 will flash with following command
afud408 a7220nms.120 /P /B /N /C
Pressing 4 will flash with following command
afud408 a7220nms.122 /P /B /N /C
Pressing 5 will flash with following command
afud408 a7220nms.133 /P /B /N /C
Pressing 6 will flash with following command
AFDOS404 A7220NMS.309 /B /C /P /N
Pressing 7 will flash with following command
AFDOS404 A7220NMS.30A /B /C /P /N
Link:
http://members.lycos.co.uk/olsen0423/MS7220
File : 7220_batch_14-45-Okt-07-2006.zip
============================================================================================
MS7125
============================================================================================
To whom it may Concern.
I made a cdom ISO for MS-7125 board also.
Menu looks like this:
1 = MS-7125 bios NCG 1.C (W7125NCG.1C0)
2 = MS-7125 bios 1.D murdok mod (7125XMOD.1D)
3 = MS-7125 bios 1.D Syar mod temp disabled (W7125NMM.1D0)
4 = MS-7125 bios 1.D MSI regular (W7125NMS.1D0)
5 = MS-7125 bios 1.C MSI regular (W7125NMS.1C0)
ISO (bootable) is at :
http://members.lycos.co.uk/olsen0423/MS7125/
D/L file: 7125_batch_22-10-Okt-15-2006.zip , unzip and burn .
Note!
Make sure that you clear cmos after bios flash (with PSU disconnected) .
After powering up , first to do is enter cmos and "Load Optimized Defaults" and setting date/time , then save/exit .
Next boot to cmos you may define/change to own preferences.
============================================================================================

Quote from: paulg on 08-October-06, 05:16:44
You're a legend syar2003! I thought I'd try v3.0a since v little is known about it and thanks to your efforts it's easy for me to revert back.
Just an initial observation on the 3.0a version - I've managed to get my 3700+ SD (E6 stepping) overclocked well beyond what I mangaged with bios v1.0. I'm now running at 2.9GHZ compared to the maximum 2.7GHZ previously - and i'm running the memory at 1:1 with the timings at stock! Seems stable enough in a windows environment (been running about 4 hours). Temps are around the 38 degree mark. I will run some Prime95 and a few 3d games over the next few days.
Thats very good , seems 3X bioses is better for overclocking afterall
Nice to be appreciated ,thanks for those kind words !
I don't have the Diamond + board myself so I can't really say if this or that bios is good or not and which versions is better or worse .
Syar

Receiver file adapter corrupting characters

Hi all,
We have an outbound article/material interface from R/3 that goes through XI 3.0 NW04 SP17 to create a flat file. The data contains characters such as and from the Czech Republic character set. As both our R/3 and XI systems are both Unicode, they seem to hold and carry through these characters fine; however, when XI creates the final output file from the message, these characters are corrupted:
túuý
becomes
¹túuý¾
In the receiver communication channel, I have tried all of UTF-8, ISO-8859-1 and ISO-8859-2 file encoding settings. The above example is from the ISO-8859-2 setting. The other two convert the problem characters to question marks ?.
Am I using the incorrect file encoding setting here or is there something else Im doing wrong?
Many thanks,
Stuart Richards

The file is correct, but when you view the file, you have the wrong codepage.
When your file is ISO-8859-2, then the characters are correct, but when you watch this and your settings are ISO-8859-1, then you see wrong characters.
= ¹
= ¾
Open the file in Internet Explorer and choose the correct codepage, then you see the characters correctly.
Regards
Stefan

ISO/IEC 8859-1 File

Similar Messages

Maybe you are looking for