FiveTech Software tech support forums

... non-East Asian languages and are not included in ANSI! E. g. Characters specific to Central and Eastern European languages (e.g., Czech, Polish, Hungarian) like Č, Ć, Đ, Ł, Ń, Ő, Ű, Ś, Š, Ž, etc., available in Latin Extended-A (ISO 8859-2). In my view, keep HB_CDPSELECT( <yourcontrycdp> ...

Hi, This is more of a brainstorming question, rather than anything technical. I'd like to stop using my variant of hungarian notation, because it doesn't really look presentable, and it doesn't fit in with standard modern practice. The way I write variables is like Account_Number_n ...

Are you using the Hungarian codepage from your app ?

FW_SetUnicode( .T. )
HB_CDPSELECT( "HUWIN" )
HB_SETCODEPAGE( "UTF8" )

http://harbourlanguage.blogspot.com.es/2010/06/harbour-codepage.html

Hi! In the newest FWH(17.11) and Harbour(3.2) I have a problem with the LisDir() and Directory() functions. My problem is the following: I use Hungarian characters (for example: é, á, í, ő, …etc.). If I use the new LisDir(“C:\é”), the function return false, incorrectly, and the Directory() function ...

... are : By default English, but they can also be displayed in any of several other languages: Czech, Danish, Dutch, Estonian, French, German, Greek, Hungarian, Italian, Japanese, Korean, Norwegian, Norwegian-ny, Polish, Portuguese, Romanian, Russian, Slovak, Spanish, or Swedish. METHOD SetLocale( ...

Rao, My point was that I wouldn't change all the fieldnames just so I could use Hungarian notation. I would change any that were necessary to avoid reserved word issues. As far as auto-incremented primary-key fields go--they worry me. Since as Reinaldo pointed out, ...

... "CODE","NAME", the column names created in states table are "ID","FCODE","FNAME". Also if we use hungarian notation, we can easily identify a field variable. if nVar, cVar, lVar denote numeric, character and logical variables, fName indicates a ...

oDBF is the alias of database Oh, and Hungarian notation says that the alias variable should be cAlias not oDBF. The "o" prefix is to signify an object. Then people like me would be able to read your code more easily. And if you were ...

... (Standard) 1036 *!* French (Belgian) 2060 *!* French (Canadian) 3084 *!* French (Swiss) 4108 *!* French (Luxembourg) 5132 *!* Hebrew 1037 *!* Hungarian 1038 *!* Icelandic 1039 *!* Italian (Standard) 1040 *!* Italian (Swiss) 2064 *!* Japanese 1041 *!* Korean 1042 *!* Korean (Johab) 2066 *!* ...

... solution. ----------------- I do note that you sometimes use a leading "o" for variable names that are not objects. This does not follow Hungarian convention and does make it more difficult for others to read and understand your code. For instance, you use oggettobmp to refer to an array. ...

Hello,

have somebody Hungarian Notation article from Antonio Linares?

regards

Marcelo

... as objects created from classes that we are used to using. And the "h" prefix is already used to signify a handle. Is there a standard Hungarian syntax for a hash table? Regards, James

I am assuming this var is an array: oSays[1]

This is not really correct Hungarian syntax. An array datatype should be prefixed with an "a" regardless of what datatype the array contains (in this case an object). So it should be aSays instead. It does contain oSay objects.

Regards,
James

... Using an array, all of the above code can be written as below. It is also not good practice to assign data of the wrong type to variables with Hungarian notation (e.g. assigning date types to variables begining with "c" then changing the type). The problem with doing this is that ...

Hi everebody! I try set code page in my applicationto hungarian. I try this code , but is not work (Browse look as english). Make I anything wrong ? Regards Andrej. /// settings REQUEST DBFCDX REQUEST DBFFPT RDDSETDEFAULT ('DBFCDX') REQUEST HB_LANG_HUWIN ...