Regardibg double byte data type in Xi(japanese character)

hi am giving japanese character(double byte) as a input data types, will you please tell me how to give whether as a string or constant ..etc. and please give information generally about double byte data type
regards,
S.K.Karthikeyan.

Hi Stefan,
I got your point it's really helpful for me.
I have one more doubt;
Is there any equivalent type for double byte char in XI ?
regards,
S.K.Karthikeyan.

Similar Messages

Problem loading PostgreSQL Bytea data type to Oracle Raw data type

We are migrating our database from PostgreSQL to Oracle. First, we convert the BYTEA data type in PostgreSQL to Oracle RAW. The BYTEA data type is variable bytes array. How can we load the BYTEA data type to Oracle RAW data type? Or I have to convert to different data type. thanks.
Peter,

hi,
Instead of 'interval day to second' in method declaration use internal datatype 'DSINTERVAL_UNCONSTRAINED'.
There are more unconstrained types in oracle.
Bartek

How to handle "byte" data type

Hi,
In web dynpro java project to consume a web service, I am unable to handle "byte" data type in binding wizard. It is not allowing to bind a element saying that "Context Attribute with Java Native Type BYTE cannot be selected". Please help me to resolve this.
Thank you.
Regards
Bhanu.

Hi
you can define byte[] in golobal area, at the end of iview.
//@@begin others
byte b1[];
//@@end
                  IWDResource r;
       byte b[];
       InputStream inputStream;
     try {
          inputStream = r.read(true);
            int x = inputStream.read(b);
     } catch (IOException e) {
          e.printStackTrace();
Regards
Anup

Unsigned byte: Java byte data type (0-255)?

I need an "unsigned" byte type.
How can I implement a one byte data type with values from 0-255 in Java?

No there isn't an unigned byte, but you don't need
one. You just separate storage representation from
calculation representation. When you store the
"unsigned byte" you use a signed byte. When you make
calculations on the "unsigned byte" you use an
integer. For this you need two conversion functions,
public static int toInt(byte b) {
return b + 128;
public static byte toByte(int i) {
return (byte)(i - 128);
}These amazing functions must be tested off course.
public void testUnsigned(int unsgn) {
byte bA[] = new byte[1];
int i = unsgn; // 0 to 255
bA[0] = toByte(i); // stored as -128 to 127
int j = toInt(bA[0]); // 0 to 255
if (i==j)
System.out.println("Yes it works!");
Sorry, but your code doesn't work. I also tried the byte & 0xFF and I get strange results too. 0xFF transfer to 129, which (I think, but maybe I'm wrong) should transfer to 255 (0xFF == 1111 1111, no?). After some tests, I found that "ounos" solution is the best fitted (byte < 0 ? b+256 : b)
If you only do a (byte + 128), you'll get, for example:
0000 0000 (should be 0) == 128
I think that only 1 case is enough to proove that this code doesn't work... :-)

Strange "+" opperator behaviour with byte data type.

This will complie:
byte counter = 1;
while (counter > 0)
System.out.println("Counter is " + counter);
counter ++;
}This will compile:
byte counter = 1;
byte one = 1;
while (counter > 0)
System.out.println("Counter is " + counter);
counter += one;
}This however will NOT complile:
byte counter = 1;
while (counter > 0)
System.out.println("Counter is " + counter);
counter = counter + 1;
}This also will NOT complile.
byte counter = 1;
byte one = 1;
while (counter > 0)
System.out.println("Counter is " + counter);
counter = counter + one;
}Why is that? The complier seems to have a problem with the + opperator with bytes, it gives me a "possible loss of precision" error.
P.S. I know these are "Infinite Loops" that was the point. I was pointing out to my instructor that even though these would be called "Infinite Loops" they do end at a specific and determinable point.

I don't see any point in using a byte for that
counter variable, except possibly to generate more
questions when it rolls past 127.I got my first programming experience back when there was only 64K of memory on my Commodore 64. Using a byte size larger than needed has always seemed wasteful to me; regardless that memory sizes are so roomy these days. I suppose it isn't even all that necessary on things like cell phones and PDAs any more. It is a little odd to me the way Java deals with bytes considering what it was originally intended to be used for. You'd think a programming language designed to be used on things like electric toasters and washing machines (or whatever, things that would not be expected to have much in the way of computing power or memory space) would require you to type cast when using small data types.
But as they say, "It's not for me to reason why, it's for me to do and type cast to a byte." Or something like that.

How to show double byte data in a Flex application

Hi
I am looking for a way to show UTF-8 formatted data in a Flex
application. I have a Java app in the backend that generates an xml
file. Some attributes in the file are encoded in UTF-8 (when data
is Japanese or Chinese...). My Flex app is showing box characters.
I have XSLT app that generates html based off this xml file. The
browser i showing the Japanese characters fine.
I am wondering what the trick is to get Flex app show this
data.
Thanks
Videoguy

It turned out to be my XP that didn't have the the right lang
sets installed. I have two PCs. On one everything showed up fine. I
was able to view arabic, chinese data from xml just fine. On the
other one, same swf didn't show them. There is MS knowledgebase
article on how to enable east asian languages etc. I didn't give it
a try. I am using other pc for my dev now.

Double byte language i.e Japanese or Chinese text in non Unicode System

Hi,
I have translated text into Chinese and Japanese in a Unicode system and want to move it into a non Unicode system. Would Chinese/Japanese characters display correctly in a non Unicode system when moved from Unicode system. I am doing translation in ECC60 or SAP 4.7 Unicode system and moving to SAP 4.7 non Unicode system.
Thanks
Balakrishna

Hi Balakrishna,
in general the transport between Unicode and Non-Unicode systems is supported.
However there are restrictions, which are outlined in SAP note 638357.
In your case it is a prerequisite that the objects to be transported are language dependent (text lang. flag is set on the language key - see SAP note 480671) and the languages are properly setup in the target systems.
For double byte data there is a specific issue when transferring data from Unicode to Non-Unicode:
In a Non-Unicode system, one double-byte character needs two bytes, therefore e.g. in a 10 char field, 5 double byte chars are fitting. In a Unicode system, you can insert 10 double-byte chars in a 10 char field. Hence there is a risk of truncating characters in case of Unicode --> Non-Unicode communication.
Please also have a look at SAP notes 1322715 and 745030.
Best regards,
Nils

Java data type - byte

Hi;
I've a question here, hopefully some one can help me to clear my doubt.
private byte[] buf = new byte[1024];
as the declaration done above, does that mean the buf can hold until 1024 bytes data? as i know, byte data type only able to hold +2 power of 8 till -2 power of 7.
YY.

private byte[] buf = new byte[1024];
as the declaration done above, does that mean the buf can hold until
1024 bytes data? Yep, you've just defined an array of 1024 bytes, all neatly lined up next
to eachother, the first byte can be retrieved or altered by indexing it like
this: 'buf[0]', the next one as 'buf[1]' and the last one as 'buf[1023]'.
as i know, byte data type only able to hold +2 power of 8 till -2 power of 7.Erm, almost; a byte can store any integral number in the range -128 to 127
inclusive, i.e. -2**7 to 2**7-1.
kind regards,
Jos

Mapping SQL data types (especially SMALLINT) to Java classes

I want to know the reason for a certain pair of exceptions in JDBC�s mapping of SQL data types to Java classes.
Sun�s web site ( http://java.sun.com/j2se/1.4.2/docs/guide/jdbc/getstart/mapping.html ), Sybase�s site, and other sites contain mappings from SQL data types to Java primitive data types and/or Java classes. On that Sun web page, Section 9.9.1 maps mostly to Java primitive data types, and Section 9.9.3 maps mostly to Java classes. For the SQL data types that map to both primitive data types and classes, the class is typically the wrapper class of the primitive data type. For example, SQL�s DOUBLE data type maps to both the double primitive data type and its wrapper class (Double). However, Section 9.7 of that Sun web page says that there are exceptions for SQL�s TINYINT and SMALLINT. As expected, they map to the byte and short primitive data types, but they map to the Integer class, not the Byte and Short classes (which are the wrapper classes for byte and short). The web page does not state the reason for this pair of exceptions. It seems to me that SMALLINT data would either work for both short and Short or fail for both short and Short. I don�t see why it would work for short but fail for Short (as the web page implies).
Can anybody think of a reason for the pair of exceptions? Thanks.

ghs wrote:
1) If a DBMS deals with the short and byte primitive data types (as the various web pages imply that it does), then why would it not deal with the Short and Byte wrapper classes?As another guess, because conversions get a little weird in java. Or at least they did in the past. As I recall (with not a lot of clarity) it is possible to do something like pass a perfectly valid string value into a short and get an exception. Whereas using Integer and then converting to Short works.
Keep in mind that these are guesses.
3) What I really want to know is this: If I use wrapper classes of Short and Byte (instead of Integer), what will be the harmful consequences (IF ANY)? So far, I have done some trivial testing with a Short for a SMALLINT column (I have not yet tried any TINYINT columns), and it seems to be working.I considered it risky to not test all target databases and drivers.
Obviously testing will reveal problems.
If you don't want to test then you might want to stick with integers.

Explain about Data Types INT1, INT2, INT3, INT4 & NUMC

could anyone explain about the data types and give examples.

INT1: 1-byte integer between 0 and 255. The length is set to 3 places for this data type.
INT2: 2-byte integer between -32767 and 32767. Fields of this type should only be used for length fields. These long fields are positioned immediately in front of a long field (type LCHR, LRAW). With INSERT or UPDATE on the long field, the database interface enters the length which was actually used in the length field. The length is set to 5 places for this data type.
INT4: 4-byte integer between -2147483647 bis 2147483647. The length is set to 10 places for this data type.
NUMC: Long character field in which only numbers can be entered. The length of this field is limited to a maximum of 255 places.
Check this:
http://help.sap.com/saphelp_nw70/helpdata/EN/cf/21f2e5446011d189700000e8322d00/frameset.htm
Thanks...
Shambhu

Double-Byte transfer from iSeries to Windows Based Central

Has anyone had success with this, and if so what steps where required to allow the double byte data to reach central in a usable format?

If you are trying to install files with quick install like you did with XP it probably did not work. If you right click on the palm file you want to install and choose send to in the drop down window. You will see Palm TM Handheld select this and they will install at the next hotsync. Clicking on them or dragging them into the quick install window did not work on either of my windows 7 computers at first. I fixed this problem on our desktop but the fix did not hold on my laptop. I am still trying to figure out a permanent fix for this problem. If this is not your current problem please explain further.

Restrict double bytes characters

Morning,
Is there a way to restrict double byte characters from being typed into a field? I am looking for an alternative to a script on the change event filtering key strikes. I've tried playing with the locale, fonts, picture clauses but didn't manage to get the desired results.
Thanks
Hélène

Thanks for your response.
We're trying to restrict double byte characters e.g. Japanese or Russian characters. The picture pattern suggested doesn't differentiate between a single and double byte character.
Hélène

How to store beyond the range value for a given data type!!!

Hi all,
I want to know.Is it possible to create a new data type like int,float in java. which can store any number without any range restrictions.As you know the range of byte data type is -128 - + 127.I don't want any range restrictions.The data type should be able to grow dynamically.
Regards!!
Tameshwar Sahu

The only solution I can think of is to use java objects, Im not sure youll be able to create a new primitive for java !!
Youd have to put together Integers, posibly in a vector depending on how HUGE a number youd like to create.
If you reached the max of one, add another to the vector. and then continue with the next.. The problem with this of course is the fact that math operations, will be a bit of a challenge to code. also actuall representation of the value would be a bit tricky as well !! There are however ways to go about this, you just have to think about it a little.

Can Double Byte Codes be used in SharePoint 2013?

Hello,
I am looking to create a SharePoint but for Japanese users. I understand that Double Byte Codes will need to be used when entering information due to the Japanese language. I have been informed that this can sometimes cause an issue with SharePoint.
I am looking to test this however I wanted to understand if this can be done / are there any considerations when using DBC's on SharePoint etc and any limitations.
Any assistance would be greatly appreciated.
Thanks
KP

Hi KP,
Yes, SharePoint 2013 supports Double Byte Unicode characters:
If you have non-standard ASCII characters, such as high-ASCII or double-byte Unicode characters, in the SharePoint URL, each of those characters is URL-encoded into two or more ASCII characters when they are passed to the Web browser. Thus, a URL with many
high-ASCII characters or double-byte Unicode characters can become longer than the original un-encoded URL. The list below gives examples of the multiplication factors:
High-ASCII characters — for example, (!, ", #, $, %, &, [Space]): multiplication factor = 3
Double byte Unicode characters — for example, Japanese, Chinese, Korean, Hindi: multiplication factor = 9
For example, when you translate the names of sites, library, folder, and file in the URL path http://www.contoso.com/sites/marketing/documents/Shared%20Documents/Promotion/Some%20File.xlsx into Japanese, the resulted encoded URL path will become something
like the following:
http://www.contoso.com/sites/%E3%83%9E%E3%83%BC%E3%82%B1%E3%83%86%E3%82%A3%E3%83%B3%E3%82%B0/%E6%96%87%E6%9B%B8/DocLib/%E3%83%97%E3%83%AD%E3%83%A2%E3%83%BC%E3%82%B7%E3%83%A7%E3%83%B3/%E3%83%95%E3%82%A1%E3%82%A4%E3%83%AB.xlsx. This path is 224 characters,
whereas the original URL path is only 94 characters.
In most cases, one UTF-16 character equals one UTF-16 code unit. However, characters that use Unicode code points greater than U+10000 will equal two UTF-16 code units. These characters include, but are not limited to, Japanese or Chinese surrogate pair
characters. If your paths include these characters, the URL length will exceed the URL length limitation with fewer than 256 or 260 characters.
Reference:
https://technet.microsoft.com/en-us/library/ff919564%28v=office.14%29.aspx?f=255&MSPPError=-2147217396
Best Regards,
Eric
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected].

Dates in BEx query coming into designer as a dimension with Char data type

This must be an old issue with a well documented work around ... but alas i can find it !
When i build a universe over a BEx query with dates the universe designer builds them as Dimensions of CHAR type not DATE. Therefore all WebI date functionality fails .. eg sorting, automatic time hierarchies etc.
What is the workaround ?
Andrew Fox

Is the data source an InfoSet or an InfoCube? It appears the date type object has not been implemented yet for Infosets. Here's SAP Note 1370410:
Symptom
Infoset date type objects (DATS type) are mapped as Character types in a universe based on a SAP BEX Query.
Prompts related to the Date field variables are coming as List of values instead of Calendar in WebIntelligence.
Reproducing the Issue
Create a BusinessOjects universe on a Super Query which is based on a multiprovider containing an Infoset or
Create a BEx superquery directly on Infoset.
BusinessObjects Enterprise XI 3.1
SAP Integrated Solutions Kit XI 3.1
Cause
This behaviour has been considered as an enhancement request and tracked under ADAPT01229917.
Resolution
This enhancement request is scheduled to be addressed in Service Pack 3 (SP3) for BusinessObjects Enterprise XI 3.1 due approximately April 2010.
I did try a BEx query that uses an InfoCUBE as a source and the objects are coming into the universe correctly as dates.

Regardibg double byte data type in Xi(japanese character)

Similar Messages

Maybe you are looking for