|
|||
|
Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exluding strings based on source sode.
|
| Moderated by: Renate.Reinartz, Markus.Kreisel, Jaakko.Salmenius, Ilkka.Salmenius | Page: 1 2 |
|
||||||||||||
| Exluding strings based on source sode. - Usage - Three simple steps to localize - Technical Support (You need to be registered at the forum to write) - Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... | ||||||||||||||
| Author | Post | |||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
|
yonik Member
|
Hello, I started the trial of the SISULIZER, I mainly need it to work with Bisual Basic 6 apps. I did not find anyway to exlude strings based on a source code line pattern. For example, my project have many of these lines: Public Declare Function CreateDIBSection Lib "gdi32" (ByVal hdc As Long, pBitmapInfo As BITMAPINFOHEADER, ByVal un As Long, lplpVoid As Long, ByVal handle As Long, ByVal dw As Long) As Long Public Declare Function GetObjectA Lib "gdi32" (ByVal hObject As Long, ByVal nCount As Long, lpObject As Any) As Long Public Declare Function SelectObject Lib "gdi32" (ByVal hdc As Long, ByVal hObject As Long) As Long Public Declare Function DeleteObject Lib "gdi32" (ByVal hObject As Long) As Long Public Declare Function GetDC Lib "user32" (ByVal hWnd As Long) As Long Public Declare Function CreateCompatibleDC Lib "gdi32" (ByVal hdc As Long) As Long Public Declare Function ReleaseDC Lib "user32" (ByVal hWnd As Long, ByVal hdc As Long) As Long Public Declare Function DeleteDC Lib "gdi32" (ByVal hdc As Long) As Long Case "ABC" Case "xyz" Case "aaa" Case "123" sCurrentProc = "MdlMain.Main" sCurrentProc = "MdlMain.GetBuyNowURL" sCurrentProc = "MdlMain.GetFileName" and etc. I want to exlude all strings in the lines that matches to these patterns: Public Declare * Case "* sCurrentProc = "* How can I preform this? Thank you, Yonik.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Yonik, you can simply add an exclude tag at the end of the line: -------------- Exclude tags If you want to disable localization of a string, add an exclude tag on the same line where the string is located. The syntax is
For example the following line contains SQL statement and it should not be localized. To disable its localization an exclude tag has been added:
This part is enabled when the Tags usage is set to Localize all but excluded. ----------- Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
I forgot to mention. In VB the command sign must be 'noslz instead of //noslz So it must be 'noslz at the end of the line for VB. Best Markus Last edited on Wed Jul 11th, 2007 03:50 pm by Markus.Kreisel ____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
yonik Member
|
Does SISULIZER have a tool that can help me track and add these tags automatically? Doing it manually will take ages, I'm working on a huge project.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hmmm, I see. Perhaps our developers have some hint or idea how to filter them out faster. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Yonik, I chated the developers his moment and there is no faster way. This is a common I18N (Internationalization) process most developers have to go through. But you will find out that using the find option in VB this might take perhaps one or two hours even for huge projects. Nothing in contrast to the time you will save later. And the good news: you only have to do it once. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
one last short issue. There is a know problem with 'noslz in the moment. It is under investigation and will be fixed in the next build. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
yonik Member
|
Hi Markus, In huge project like I'm working on it will take much more then few hours. I'm talking about 1000's of such code lines. Also doing it manually may cuase to hidden bugs do to the human factor. I testes some other and chipper tools and they all had this filtering option. Your tool looks like one of the best so I expected you to have this filtering option too. Without such filter tool I can't see how can I do the task using SISULIZER
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Yonik. I asked you in a private message for the names of the other tools you have in mind so we can take a look at it and analyze what they do. Please send me their names in a private message. You always should keep in mind, that I18N is a very small part of the job and of the costs. If you choose a tool that has some advantages here but lacks later with translation reuse or has trouble with Far East character sets you will run into major extra costs with your translators. And you should not forget technical support. If you buy cheap the vendor might not be interested or able to help you at a time you mostly need it. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
yonik Member
|
Hi Markus, I agree that your product looks like a good investment and so far your support is very fast. I will replay you privatly. Thank you, Yonik.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Ilkka.Siikanen Administrator
|
I will impement to the next buid (1.5.19) a feature that allows to enter excluded string by wild cards. like: Public Declare * Case "* sCurrentProc = "* best regards Ilkka
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Yonik, we are discussing internally how useful such feature would be for all platforms and how much extra work load it would mean to the team. Our WPF beta has just started and we are all already quiet busy. We know about the importance of a good support. Just take VB and the support of these .frx files some properties need. These format is not documented at all, but sometimes contains a lot of strings to be translated. It would be a lot of work if you have to set these properties manually in your code while your tool can not read them from .frx. We also can not support them all. There are third party controls storing whole menus with panels and so on in one data segment of the .frx. In this cases it is impossible to read these because they are unknown binary data. A prominent sample is ActiveBar. But for this we know some nice work arounds. While we support most data in .frx I'm very curious about competitors here. I doubt that they have gone this extra mile of .frx support :-) Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
... Ilkka, you are always faster than me :-)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
yonik Member
|
Markus, Ilkka Thank you, this will be great. I like your product and I'm sure adding this feature will make it much more user friendly to everyone dealing huge classic vb projects. p.s. if you make this feature using on-line filtering during the scan (without changing the original source code or adding tags to it) it will be the best. That way the developer can be sure that no one else has alter the source code. I will be waiting for the next release, Thank you, Yonik.
|
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
Hi Yonik, stay tuned while we are very fast. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Jaakko.Salmenius Administrator
|
1.6.0 is available http://www.sisulizer.com/downloads.shtml Jaakko
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
yonik Member
|
Hello, I came back to see if you added the support for the above topic I oppend. I saw that you reffer to a new version (v1.6.0) but I didn't see this new feature (excluded string by wild cards) on the new features of this version. Does v1.6.0 includes this new feature? Thank you, Yonik.
|
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
Ilkka.Salmenius Administrator
|
Choose Project | Options... menu Attachment: Options.PNG (Downloaded 43 times)
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
|
||||||||||||||
|
Markus.Kreisel Administrator
|
One little issue. To make use of that it is important to know, that the filter works on the extracted string and not on the source code line. So if you want to exclude "user32" from Public Declare Function GetDC Lib "user32" (ByVal hWnd As Long) As Long you can not enter "Public Declare *". You have to enter "user*" to get rid of the string for translation. Best Markus
____________________ http://www.sisulizer.com - Three simple steps to localize |
|||||||||||||
| ||||||||||||||
| ||||||||||||||
|
yonik Member
|
This makes the tool not very usefull I have tones (Thousands) of lines like: Case "ABC" Case "xyz" Case "aaa" Case "123" and like: sCurrentProc = "MdlMain.Main" sCurrentProc = "aaa.GetBuyNowURL" sCurrentProc = "bbb.GetFileName" I need to exclude all the Case "* code lines. How can I preform this? The same for the sCurrentProc = "* lines, how can I exlude them? Most of the lines do not have any common string pattern! the only have common code pattern. The excluding should be based on the code pattern, otherwise the tool is not usefull
|
|||||||||||||
| ||||||||||||||
| Current time is 09:24 pm | Page: 1 2 |
| Localization Tool for VB, Delphi, .NET, C#, VB.NET, XML, Online Help, HTML ... > Technical Support (You need to be registered at the forum to write) > Usage - Three simple steps to localize > Exluding strings based on source sode. | |
Sisulizer software localization tool - Three simple steps to localize