|
|
 |
 |
 |
 |
TCL(Tool Command Language) Scripting
|
 |
 |
 |
 |
 |
 |
 |
 |
encodings in Starkit
I am trying to include a full range of encodings in a Starkit, not just the default nine. I should presumably be able to do this by creating a directory containing copies of the encoding files within the vfs. However, I have been unsuccessful in doing this. According to the documentation, tcl looks for encoding files in an encoding subdirectoryof each of the directories mentioned in tcl_libPath, and tcl_libPath is presumably set to vfs/lib/*, so I would think that I could put the encoding subdirectory within any of the subdirectories of lib. None of these work, nor does putting the encoding directory directly under vfs/lib work. So, how does one include additional encodings in a Starkit? Thanks.
Hi and good morning from Berlin/Germany, I recently put all tcl 8.5 encodings into a starpack to support more than the default ones and had no problem. I created following directory structure inside the VFS: ...\application.vfs\lib\tcl8.5\encoding It worked without any problems! So - if this fails I don't know what to tell you! Best regards, Martin Lemburg Siemens Automation and Drives - UGS PLM Software On May 14, 12:00 am, billpo@alum.mit.edu wrote:
> I am trying to include a full range of encodings in a Starkit, not > just the default nine. I should presumably be able to do this by > creating a directory containing copies of the encoding files within > the vfs. However, I have been unsuccessful in doing this. According to > the documentation, tcl looks for encoding files in an encoding > subdirectoryof each of the directories mentioned in tcl_libPath, and > tcl_libPath is presumably set to vfs/lib/*, so I would think that I > could put the encoding subdirectory within any of the subdirectories > of lib. None of these work, nor does putting the encoding directory > directly under vfs/lib work. So, how does one include additional > encodings in a Starkit? Thanks.
On May 13, 6:00 pm, billpo@alum.mit.edu wrote: > However, I have been unsuccessful in doing this. ... > None of these work, nor does putting the encoding directory > directly under vfs/lib work.
Could you describe the behavior that indicates that "none of these work"?
On May 14, 5:32 am, "Larry W. Virden" <lvir@gmail.com> wrote: > On May 13, 6:00 pm, billpo @alum.mit.edu wrote: > > However, I have been unsuccessful in doing this. > ... > > None of these work, nor does putting the encoding directory > > directly under vfs/lib work. > Could you describe the behavior that indicates that "none of these > work"?
Thanks very much. The behavior that showed that "none of these work" is that when I brought up a menu whose entry were populated by [encoding names], I only got a list of nine encodings rather than the list of 82 encodings I expected. It turns out my problem was a simple spelling error. When I converted the scripts for creating the Starkit into a Makefile, I called the directory containing the encoding files "encodings", with an "s", rather than the correct "encoding". Your message alerted me to the error and everything now works just fine.
On May 14, 11:46 am, billpo@alum.mit.edu wrote: > Your message alerted me to the > error and everything now works just fine.
:-D - I love it when a request for more information results in an answer to a problem. It is so much better than those times when you call in a maintenance person (or take an item into a repair shop) and there's no way to demonstrate the problem...
|
 |
 |
 |
 |
|