Dear Mark,
First of all I want to thank you
from my heart the help you are giving to me and others on the list.
Your positive and detailed responses makes me feel secured
that atlest someone is there to
solve my queries.
Keep on the good work!brother.

Some more queries..

1. As my CD image creation program is for Windows platforms.There both ':'
and "\0" are invalid characters for filenames.So, I wont face the problem,i
believe.
I will be using "TCHAR*" than "char*" for strings .My aim is HFS CD
image.So,can u tell me if the
end user selects some files from a Windows volume(eg. Korean windows)that
means filenames will
be in Korean then the HFS image(which I will create from the selected files
by the End user)
will not be "understood" by a Mac machine (for eg. in English)or
vice-versa.Am I right???

2. As u said Mac OS supports many character encodings.Is there any field in
the HFS volume
   where information about the character set used is stored?

3. (Most Important for me)please suggest.
     For my understanding I am reffering to "mkhybrid" and "mkhfs"
application code and trying
   to do it on Windows. You must be already aware of these premastering
applications for Linux.
   I am trying to understand the implementation logic of the B*tree from
them and how they
   create the Image file. I just want an answer Whether my approach is
correct and what more
   I should be in touch?? As far my understanding the latter part is going
to be same(I mean the logic of creating the HFS filesystem will be same)only
the selection of files and their validations will be different??

Waitng for your answers anxiously!
regards
Biswaroop Banerjee