If ExamineDirectory(1,GetPathPart(ProgramFilename()),"*.*")
While NextDirectoryEntry(1)
If LCase(GetExtensionPart(DirectoryEntryName(1))) = "nxscribelan"
languagefilename$=DirectoryEntryName(1)
Break
EndIf
Wend
FinishDirectory(1)
EndIf
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
With all the libraries nxScribe is using (all my own except one!) the source comes to 10000 lines of code and I didn't fancy trawling through that little lot!
I must remember that problem with ExamineDirectory() and Win NT. Sure is a strange one!
Thanks for all of your help Philippe, you certainly are one patient fellow!
I may look like a mule, but I'm not a complete ass.
10th Oct 2007. Update - nxScribe version 1.0 beta 2.
My thanks to all those who have tested out the first beta. Particular thanks to Gnozal and fangbeast for really going out of their way to help out.
Beta 2 sees the following alterations :
Individual language files can now be saved in Purebasic preferences format (as in beta 1) or XML (utf-8 ) format (new for beta 2). I've tested the resulting XML files with IE 6 and they seem well formed etc.
Use XML format if you require trailing spaces with your language strings etc.
Individual language strings now retain their leading and trailing spaces (bug fix).
The toolbar icons no longer appear dithered (bug with the nxToolbar library which is now fixed). My thanks to fangbeast for this.
Grid columns are now resizeable.
Bugs with keyboard shortcuts fixed.
Added a button for adding rows to the grids used to edit language strings. You can still use the context menus however.
Fixed an issue causing nxScribe to crash out on Win NT. Still remains to be seen whether this new version will run on NT however? (Gnozal? )
Altered a few other things, but can't remember what they were now!
I've still to add the code generation and the help manual.
The download link is in the first post.
I may look like a mule, but I'm not a complete ass.
Hi srod, seems like there is a problem writing out unicode chars with this beta. Japanese chars are being corrupted when being written out in nxScribe and lan files (normal & utf8). This wasn't a problem in the first beta. I noticed this time it seems the nxScribe (& xml) is written out all on the one line (no CRs) unlike the first beta. Is this ok?
Last edited by mskuma on Wed Oct 10, 2007 11:50 pm, edited 1 time in total.
I've just tried some Hebrew characters and whilst you just get the standard looking blocks whilst viewing the project file in Notepad, the characters appear fine when viewing in IE or Word.
I'll test a little more.
I may look like a mule, but I'm not a complete ass.
Yes, the 'jaggies' have gone on the buttons, looks nice and smooth here.
Thanks for the INSert shortcut, my aching wrist is happy. Got up this morning and this is the first thing I tried (after the loo of course!!) Haven't even had breakfast yet so there!!!
Am busy recreating my Addresser project in this. Thanks for the hard work.
Oi, Sparkie, get off my head, you are too heavy!!!
/me falls off the chair again that srod promised would hold him
*EDIT* Suggestion: Add a splitter gadget between the editing area and the Languages/Language groups to give the string editing are more room to work.
I wouldn't go too far with the addresser conversion just yet fangles, not until I get to the bottom of the xml / unicode / utf-8 issue!
I understand, but the only way to find more bugs is throw strings at the beast and see how she roars. Addresser has hundreds of strings and is a good test for nxscribe.
srod wrote:[*]Fixed an issue causing nxScribe to crash out on Win NT. Still remains to be seen whether this new version will run on NT however? (Gnozal? )
It's ok now. No more crash.
For free libraries and tools, visit my web site (also home of jaPBe V3 and PureFORM).
