FiveTech Software tech support forums

Thanks for you reply. This is the result which is shown: cTxt_dri : &é"'(§è!çà)-âêîûôäëïöü OemToAnsi ( cTxt_dri ) : &Ú"'(ºÞ!þÓ)-ÔÛ¯¹¶õÙ´÷³ AnsiToOem ( cTxt_dri ) : &‚"'(õŠ!‡…)-ƒˆŒ–“„‰‹” It is strange that the problem does NOT occur in FWH 13.07. ...

... ):Value , ; dtoc( oRS1:Fields( "Fec_modi" ):Value) ; headers "Discont", "Código", "Cód.Barra" , ; oemtoansi( "Descripci¢n" ), "Ult. Proveedor", ; "costo" , ; "UM", , "Ult.Modif" ; LINES CELL font ...

Yes, pure sql works! Without AnsiToUtf8()! Because I have completely switched from mixed ASCII-Cp850/Ansi environment to UTF8, i.e. source code (UEStudio) and database DBF/MariaDB. From now on, I no longer have to worry about the encoding. No more conversions between the code pages HB_OemToAnsi()/HB...

Hola gente, tengo definido este listbox REDEFINE LISTBOX oLbx FIELDS ; str( oRSRub:Fields( "rubro" ):Value, 3 ), ; oemtoansi( oRSRub:Fields( "descri" ):Value ) ; HEADERS oemtoansi( "N£mero" ), oemtoansi( "Descripci¢n" ) ; // ON dblCLICK (editrubro(olbx,.F.), ...

... Use un EDITOR mejor.    TASKGROUP  "Detalles" NO COLLAPSABLE      /*      TASKITEM  "<b>TTaskPanel()</b>" + ;      OemToAnsi("<p>Clase para la creaci¢n de paneles de tareas</p>")+;                "<p><b>Autor</b></p>" ...

After doing several tests, I came to the opinion that it is not a good idea to make our functions. It is better to depend on the standard Harbour function OemToAnsi() and then later convert to Utf8 if necessary.

... UTF8 So we can use: UTF16toUTF8( strToWide( UML_OEMTOANSI( fieldGet( n ) ) ) ) Please use UML_OEMTOANSI() but not OemToAnsi() YES this "seems" to work, no Error in LOG :D but when try to open Excel Sheet i got Warning and all Type "C" are empty ...

... ) So we can use: UTF16toUTF8( strToWide( UML_OEMTOANSI( fieldGet( n ) ) ) ) Please use UML_OEMTOANSI() but not OemToAnsi()

hi, thx for your Sample i have try OemToAnsi() before and now also UML_OemToAnsi() ... but this is not the Problem i have disable *   hb_LangSelect( cLangCode )*   hb_cdpSelect( cCodepage )*   FW_SetUnicode( .T. )USE ...

... .T., "UMLA" )   SELECT UMLOEM   DBEVAL( <||         UMLA->( DBAPPEND() )         UMLA->FLD1  := OEMTOANSI( UMLOEM->FLD1 )         UMLA->FLD2  := OEMTOANSI( UMLOEM->FLD2 )         return nil         > )   CLOSE DATA  ...

... By the way you remind me of programming with CP/M (8-bit) those days. but there is no OEMtoUTF8() Function in FiveWin, or :idea: But we have OEMtoANSI() function. Is it useful for conerting German Umlauts to ANSI? Once we convert to ANSI, we can easily convert to UTF8 and we discussed this ...

... 0 // marca opcion principal del menu MENU case TablaMnu[i,2] == 1 // subopcion del menu if ! Empty( cAccion := TablaMnu[i,5]) MENUITEM ( AllTrim( oemtoansi(TablaMnu[i,3]) ) ) ; BLOCK &( cAccion ) ; MESSAGE ( AllTrim( oemtoansi(TablaMnu[i,4]) ) ) ; FILENAME TablaMnu[i,6] * COLORMENU CLR_RED, ...

... la "Ñ" correctamente los que están en codificacion dos me muestran la "Ñ" así "¥" Si en la impresión hago un oemtoansi, la que tiene codificacón DOS se muestra correctamente, pero la que tiene codificación ansi se muestra mal. he intentado con strtran(poblacion,"¥","Ñ"), ...

Y poque no lo pones en la linea directamente

Code: Select all  Expand view

oPrn:Say(prow, pcol*5 ,Replicate("═", 90) ,oCour_n_10)
 

Es decir, poniendo directamente en el editor. A mi en mi editor no me hace falta poner el oemtoansi. Me coge el caracter directamente, como °, © etc.

... con esta libreria yo hago: Para una fecha: @ nFila, nCol XLS SAY "Fecha:" + DTOC( Date() ) OF oXls Para un texto: @ nFila, nCol XLS SAY OemToAnsi( cText ) OF oXls Para un número, antes tengo que dar formato: DEFINE XLS FORMAT nFormat PICTURE '#,##0.00' Y no he visto otras formas de hacerlo