JosDuchIt wrote:I don't find any standard describing how a .CT file generated with catcomp from a .cd file must be filled in
To begin with: in the .CT file i find
## version $VER: XX.catalog XX.XX (XX.XX.20XX)
## codeset X
## language X
the cd file has a version string, if this is the one i should use , why doesn't catcomp fills in that version?
Ah! Good.JosDuchIt wrote:@nbache
i did find out i was using an old version of catcomp sitting in sys:utilities
Correct, the COMMENTS argument is just what I always use and recommend, because it leaves the original texts in the .ct as comments, so it's easier to see what you translate.V 53.1 of the SDK works as mentioned, it does not even need the COMMENTS argument
Yep, that's correct (well, except for the missing x in the first filename ). If all three files have the same basename (the part before the "."), you should also be able just to use "Catcheck example".Could you also post the commandline(s) you use most for catcheck ?
OK it seems that it has to be
catcheck CD eample.cd CT example.ct CAT example.catalog
/* LaunchCatcheck.rexx launch */
OPTIONS FAILAT 20
Catcheck CD 'sys:Locale/catalogs/BetterString_mcp.cd' > 'env:.Local_CatCheckResult'
/* 'Notepad env:.Local_CatCheckResult' * / * resulted in lines t 0 \n Commande Inconnue. Notepad was opened the file existed in env; but the file was not loaded in Notepad */
/* Notepad 'env:.Local_CatCheckResult' * / * idem */
Users browsing this forum: No registered users and 1 guest