Leaderboard

Latest update just released. See below for change log.

To the contrary. Decomposing composed characters is a complex but formal process obeying strict rules.The reverse process: transforming form D to form C is symetric so you can round trip from form C to form D to form C verbatim. Whatever combination of diacritics you add to "A", the base letter still remains "A". "À" (a precomposed Unicode character) decomposes to "A" followed by "`" (grave accent). Hence there is nothing arbitrary there. Other normalization forms (those with a K) operate on compatibility [de]composition while those without K are based on canonical (strict) equivalence. Compatibility means that things are not always reversible in all cases. For instance the fraction character ¼ is compatibity-decomposed into the ASCII 1/4.

@Exit unsure of what was different but after running today it works perfectly thanks for answering quickly though 🙂

https://www.autoitscript.com/autoit3/docs/functions/TCPSend.htm

I was just trying to make it fairer, I don’t even want to know how bad it would get trounced with the best compiler/env ..

So just for the hell of it I installed gcc under wsl and compiled an exe that was nothing more than a for loop to 1000000000. It ran 15 times faster than the same functionality via an autoit executable. Not dissing autoit, but whats your take on the speed differential on something super primitive like a for loop? I'm sure that gcc optimizes it well, but how much is there to do? Do you think, in this case, that its because of variant math that eats up the time?

The script ends immediately right after the start ( before you can press F2). You will need e.g. a main loop. HotKeySet("{ESC}", "_Terminate") HotKeySet("{F2}", "GG") Local $wait = 1000, $left = 0, $right = 0 ; -------------- Main-Loop ----------------- While 1 Sleep(100) WEnd ; ------------------------------------------- Func GG() While 1 Progress($left, $right) Send("{LEFT}") Sleep($wait) $left = $left + 1 Progress($left, $right) Send("{RIGHT}") Sleep($wait) $right = $right + 1 Progress($left, $right) WEnd EndFunc ;==>GG Func Progress($left, $right) Local $hotkey = "" If @HotKeyPressed = "{F2}" Then $hotkey = "You Are gooood" EndIf ToolTip("Hotkey: " & $hotkey & " " & @HotKeyPressed & @CRLF & _ "Left: " & $left & @CRLF & _ "right: " & $right & @CRLF & _ "Time: " & time($left, $right), _ 400, 500, "_____Thanks so much!_____") EndFunc ;==>Progress Func time($left, $right) $totalSecs = (($left - $right) * $wait) / 1000 $hrs = Floor($totalSecs / 3600) $mins = Floor((($totalSecs / 3600) - $hrs) * 60) $secs = Floor((($totalSecs / 60) - Floor(($totalSecs / 60))) * 60) Return $hrs & " HR: " & $mins & "MIN: " & $secs & " S" EndFunc ;==>time Func _Terminate() ConsoleWrite("! Script terminated by user" & @CRLF) Exit; EndFunc ;==>_Terminate

Use this to unaccent your strings: ; Unicode Normalization Forms Global Enum $UNF_NormC = 1, $UNF_NormD, $UNF_NormKC = 5, $UNF_NormKD Func _UNF_Change($sIn, $iForm) If $iForm = $UNF_NormC Or $iForm = $UNF_NormD Or $iForm = $UNF_NormKC Or $iForm = $UNF_NormKD Then Local $aRet = DllCall("Normaliz.dll", "int", "NormalizeString", "int", $iForm, "wstr", $sIn, "int", -1, "ptr", 0, "int", 0) Local $tOut = DllStructCreate("wchar[" & 2 * ($aRet[0] + 20) & "]") $aRet = DllCall("Normaliz.dll", "int", "NormalizeString", "int", $iForm, "wstr", $sIn, "int", -1, "ptr", DllStructGetPtr($tOut, 1), "int", 2 * ($aRet[0] + 20)) Return DllStructGetData($tOut, 1) Else SetError(1, 0, $sIn) EndIf EndFunc ;==>_UNF_Change Func _Unaccent($s, $iMode = 0) Local Static $aPat = [ _ "(*UCP)[\x{300}-\x{36F}`'¨^¸¯]", _ ; $iMode = 0 : remove combining accents only "(*UCP)\p{Mn}|\p{Lm}|\p{Sk}" _ ; $iMode = 1 : " " " and modifying letters ] Return StringRegExpReplace(_UNF_Change($s, $UNF_NormD), $aPat[Mod($iMode, 2)], "") EndFunc ;==>_Unaccent Local $s = 'Nếu tôi là cậu thì sẽ biết mệt mỏi' Local $t = _Unaccent($s) MsgBox(0, "", $s & @LF & $t) This has nothing to do with UTF8, let alone unsigned UTF8 (which doesn't make sense).

Mine is basically a wrapper for the Microsoft Win32 HttpAPI APIs. The benefit is that it is documented by Microsoft, there are numerous examples of its implementation on the web, and the Win32 APIs use HTTP standards for communication. This is another light-weight web server that is built upon a different framework. It might be even easier to implement than the HTTPAPI UDF because it is designed specifically around wrapping web services around AutoIt scripts.