![]() ![]() They aren't even hard or arcane anymore now that the syntax has been replaced with things like and and so on.Process: RapidWeaver 8 Path: /Applications/RapidWeaver 8.app/Contents/ MacOS/RapidWeaver 8 Identifier: Version: Code Type: Parent Process: Responsible: User ID: 8 8.7 (20860) X86-64 (Native) ? RapidWeaver 8 501 Date/Time: OS Version: Report Version: Bridge OS Version: Anonymous UUID: AC72F9DC3A16 Sleep/Wake UUID: B1BB-4CAB-9D55-5A3011217F1A Time Awake Since Boot: 95000 seconds Time Since Wake: 26000 seconds System Integrity Protection: disabled Crashed Thread: 10 Dispatch queue: NSOperationQueue 0x7fdd4f26b2a0 (QOS: UNSPECIFIED) Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Application Specific Information: abort() called RapidWeaver 8(798,0x700008aae000) malloc: Incorrect checksum for freed object 0x7fdd4f0d4b98: probably modified 19:40:10.814 +0200 macOS 11.0.1 (20B28) 12 3.0 (14Y908) FF18B496-D668-9DA8-EDE2- 748B4E7A- after being freed. However, the basic issue that arises here, and with this problem in general, is very, very easily solved with the country codes. So that kind of thing would still need addressed, but would be an easy fix too just involving, say, a simple lookup one could add though it'd be "fun" setting up the lookup table for each language one wanted to accomodate. In other words, Excel would not think that even though you specified a country and language that you still wanted, say, Dutch or Congolese month names. I have no way to test the following, but I assume that if one were to use a format that displayed day of the week names or month names, they would be from the same language set. The rest of the string uses codes from that set so it would interpret them properly and send an appropriate string back to TEXT() for it to display in the cell (and pass on to other formulas if such exist). It would then drop the usual set of formatting codes it loaded upon starting up and load in the formatting codes for English ("en") and in particular, US English ("US"). The function would then read the formatting string and see the language code. Rather than giving an #ERROR! as it would for "horse" or -6. ![]() ![]() The function would collect the value in A1, ask Excel to treat it as a date, Excel would and would say fine, it's cool (i.e.: the value is, say, 43857 and not "horse") because it is a positive number which is a requirement for anything to be treated as a date, and let the function move on to rendering it as a date in the manner prescribed. So I'd want to use them and to ensure they "come out" regardless of anyone's Windows or Excel version, or the country they are in, I'd do it like the following (for TEXT(), let's say, but it'd be the same idea in custom formatting): =TEXT(A1,"dd-mm-yyyy") The easy fix, whether directly custom formatting a cell or using TEXT(), is to use a country code for a language you know the proper formatting codes for.įor instance, I am in the US, have a US version of Excel, and am familiar with its date code formats. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |