KudoZ home » Japanese to English » Computers: Systems, Networks

ホスト名は沸可範囲内で沸

English translation: =ホスト名は表示可能範囲内で表示... (host name is displayed to the extent ...)

Advertisement

Login or register (free and only takes a few minutes) to participate in this question.

You will also have access to many other tools and opportunities designed for those who have language-related jobs
(or are passionate about them). Participation is free and the site has a strict confidentiality policy.
GLOSSARY ENTRY (DERIVED FROM QUESTION BELOW)
Japanese term or phrase:ホスト名は沸可範囲内で沸
English translation:=ホスト名は表示可能範囲内で表示... (host name is displayed to the extent ...)
Entered by: xxxckapel
Options:
- Contribute to this entry
- Include in personal glossary

08:51 Mar 13, 2008
Japanese to English translations [PRO]
Tech/Engineering - Computers: Systems, Networks
Japanese term or phrase: ホスト名は沸可範囲内で沸
I can't seem to find the meaning of 沸 in this context.

Thanks,

Corinne
xxxckapel
Local time: 04:28
=ホスト名は表示可能範囲内で表示... (host name is displayed to the extent ...)
Explanation:
No, I'm not a code breaker, but I have done localization for quite some time and have seen this in the past. 表示 turned into 沸.

You might run into more "odd", out-of context characters, and so my advice is to contact your client immediately and alert them that the some Japanese characters are garbled.

I said it "in the past" because this was the case with some compilers, but it should have been fixed for some time. I cannot tell you when this happened, but if you are looking at Trados Workbench or Multiterm, the chance is that this corruption happened during the alignment stage. Or, the Japaese texts were handled in a non-Japanese environment.

Here is a bit of technical background, if you are interested:

It only happens with certain Kanji whose trail byte (Kanji is double-byte, consisting of a lead byte and a trail byte) is 5C (in hex). 5c is Backslash in ASCII, and the parser thinks it is a backslash , which is an escape character in some environments, and skips reading the very next byte (the lead byte of the next character). So, 沸 is the result of

lead byte of 表 + trail byte of 示.

Some of the Kanji that cause the same problem are:

ソ、能、表、予、十、貼、構

And how they become depends on what follows these kanji.

Good Luck!

--------------------------------------------------
Note added at 6 hrs (2008-03-13 15:18:24 GMT) Post-grading
--------------------------------------------------

Hi Corinne,

Both Kathy's and your comments let me further -- This problem still happens easily with web pages or html/xml based help files. If possible, check with your client if the encoding specification is set properly. good luck!
Selected response from:

RieM
United States
Local time: 07:28
Grading comment
Thanks so much now it makes sense. It's strange because i have 表示 a few sentences later and it is fine.
Anyway, computers!!!!!
誠に有り難う

4 KudoZ points were awarded for this answer

Advertisement


Summary of answers provided
4 +2=ホスト名は表示可能範囲内で表示... (host name is displayed to the extent ...)
RieM


Discussion entries: 5





  

Answers


5 hrs   confidence: Answerer confidence 4/5Answerer confidence 4/5 peer agreement (net): +2
=ホスト名は表示可能範囲内で表示... (host name is displayed to the extent ...)


Explanation:
No, I'm not a code breaker, but I have done localization for quite some time and have seen this in the past. 表示 turned into 沸.

You might run into more "odd", out-of context characters, and so my advice is to contact your client immediately and alert them that the some Japanese characters are garbled.

I said it "in the past" because this was the case with some compilers, but it should have been fixed for some time. I cannot tell you when this happened, but if you are looking at Trados Workbench or Multiterm, the chance is that this corruption happened during the alignment stage. Or, the Japaese texts were handled in a non-Japanese environment.

Here is a bit of technical background, if you are interested:

It only happens with certain Kanji whose trail byte (Kanji is double-byte, consisting of a lead byte and a trail byte) is 5C (in hex). 5c is Backslash in ASCII, and the parser thinks it is a backslash , which is an escape character in some environments, and skips reading the very next byte (the lead byte of the next character). So, 沸 is the result of

lead byte of 表 + trail byte of 示.

Some of the Kanji that cause the same problem are:

ソ、能、表、予、十、貼、構

And how they become depends on what follows these kanji.

Good Luck!

--------------------------------------------------
Note added at 6 hrs (2008-03-13 15:18:24 GMT) Post-grading
--------------------------------------------------

Hi Corinne,

Both Kathy's and your comments let me further -- This problem still happens easily with web pages or html/xml based help files. If possible, check with your client if the encoding specification is set properly. good luck!

RieM
United States
Local time: 07:28
Specializes in field
Native speaker of: Japanese
PRO pts in category: 16
Grading comment
Thanks so much now it makes sense. It's strange because i have 表示 a few sentences later and it is fine.
Anyway, computers!!!!!
誠に有り難う

Peer comments on this answer (and responses from the answerer)
agree  KathyT: Rie, you are amazing! I am totally convinced by your explanation. Fwiw, the Proz site ALWAYS used to garble 表示、表現、etc. until they switched to Unicode. Remember that, anyone?
7 mins
  -> Thank you, Kathy. This is a "been there done that" thing to me. Back in the *old" days, the engineer had to insert a backslash after these Kanji instances so that they were passed properly. (correction made :-))

agree  Angel Yamada: When starting to read, I admit I thought you were a cryptologyst, but certainly is a good explanation. Thank you.
15 mins
  -> Thank you.
Login to enter a peer comment (or grade)




Return to KudoZ list


KudoZ™ translation help
The KudoZ network provides a framework for translators and others to assist each other with translations or explanations of terms and short phrases.



See also:



Term search
  • All of ProZ.com
  • Term search
  • Jobs
  • Forums
  • Multiple search