It seems to me that English texts will get better hyphenation if the system language in macOS is set to English. Thing is, it is hard to be sure, and restarting with a new system language is cumbersome, so I haven't tested this thoroughly, but I'm reasonable sure that I've only seen "somet-hing" and similar when my system was set to Swedish.
This is on macOS Big Sur, in an NSTextView with hyphenation switched on by setting hyphenationFactor to 1 on an NSParagraphStyle object in an NSAttributedString. It is not a web view. The application is not localized, so the app language is English even when the system is set to Swedish. Setting NSAccessibilityLanguageTextAttribute to "en-US" seems to have no effect.
I'd like to know if anyone can confirm this, and if so, can anything be done about it?
From the documentation of hyphenationFactor:
This property detects the user-selected language by examining the first item in preferredLanguages.
+[NSLocale preferredLanguages] is called once from -[NSAttributedString lineBreakByHyphenatingBeforeIndex:withinRange:] but before that the language is read from NSUserDefaults with key NSHyphenationLanguage. Setting the language with
[NSUserDefaults.standardUserDefaults setObject:#"en" forKey:#"NSHyphenationLanguage"]
seems to work but it is undocumented, so use it at your own risk.
I have had this issue for a while, and now, after a fresh install of macOS I am plagued with it again, so, I am sure this isn't the result of some custom program running on the machine. I only have macOS Big Sur and IntelliJ IDEA (I had Catalina before with the same results).
Whenever I try to refactor code to introduce a new parameter using Command-Option-P, the preferences window pops up. This is beyond annoying, and I would rather not throw away years of muscle memory by remapping my extract parameter shortcut to something else.
Has anyone experienced this, and if so, what is the way to fix this?
Thanks to the comment by #CrazyCoder who looked into this.
This is a known issue with the "ABC - Extended" keyboard selection on the macOS. I like this keyboard for the range of optional characters it gives me. But apparently, there is a known issue that prevents correct behavior in this case: https://youtrack.jetbrains.com/issue/IDEA-242986
I just downloaded Aptana 3 built 3.61.201410201044 and i'm experiencing an issue:
Everytime i try to type the question mark "?" aptana enable/ disable "Show whitespace characters" option
I tried using both Shift+/ and AltGr+w and it didn't work
Even if i copy/paste a text that use the character, it doesn't work on my method when running.
I'm on Windows 7; my keyboard is PT-Br and all the encodings (default and each file) are set to UTF-8
I don't know what to do, as i need this symbol to use many methods in Ruby...
I googled this issue for a long time before asking here, and just read about setting the encoding to utf-8 but i did it and didn't work.
Please help
Well, after many tries i found how to solve it. I'll post here just in case somebody else need:
Go to
Preferences> General> Keys
then search for "Show whitespace characters" and delet the binding (keys shortcut / hotkeys)
I maintain a PowerBuilder Classic 12.5 application which has functionality to print checks on a Source Technologies MICR printer. The application has been running fine in a Windows XP environment. We are trying to move to a Windows-7 operating system and the check printing no longer works.
Here is the issue. PowerBuilder issues a PrintOpen followed by several Print commands to send command strings to the printer to unlock MICR mode and various secure fonts:
il_job = PrintOpen( )
Print(il_job,'&%STF[password]$')
Print(il_job,'&%SMCPFFFF$')
Print(il_job,'&%STP10003$')
Print(il_job,'&%STP10002$')
Print(il_job,'&%STP10001$')
Print(il_job,'&%1B$&u600D')
Print(il_job,'&%1B$*t600R')
This works fine on XP, and if you redirect the printer to "print to file", you can see the command strings right there in the file.
In Windows-7, the printer does not recognize the command strings, and in fact, just prints the commands on the check stock. If you do the same "print to file", you can see the commands in there, but each character in the command string is separated by other characters.
The following is a sample taken from the "print to" file, and you can see the string '&%SMCPFFFF$' by looking at each character that precedes an asterisk (*).
*p171Y&*p50X%*p100XS*p150XM*p200XC*p250XP*p300XF*p350XF*p400XF*p450XF*p500X$
This would seem to be a print driver issue, and in fact, Source Technologies now provides a "Universal Print Driver" which we have been told to use. Our PC support person was able to get the check printing working temporarily by re-installing the old print driver that we used on Windows XP, but as soon as the printer is turned off and on again, it resets to the new universal driver.
I tried using PrintDefineFont and PrintSetFont, to set the font to Courier Regular 8pt (which is what the Tech Support guy at Source Technologies told us we needed), but that didn't help:
PrintDefineFont(il_job, 1, "Courier", -8, 400, Fixed!, AnyFont!, FALSE, FALSE)
PrintSetFont(il_job, 1)
Can anyone help me with this issue? Or suggest where I might get help.
Thanks.
Try this: Add a new printer. Select the port your printer is connected to. Select Manufacturer: Generic, Printer: Generic/Text only. When you print to this printer it should send exactly what's in your Print statements to the printer.
Thanks Hugh, I tried your suggestion which sounded good, but unfortunately it had no effect.
As it happens, as of yesterday I did resolve the last of the printing issues. I had to address each of the special fonts (micr line, signature, check amount etc.) individually, and used a combination of using PrintDefineFont/PrintSetFont, embedded printer command strings to reset the font, and changing a Column control in the datawindow to a Text control (a printer command string is moved into this field as well as the data, and the one worked, the other didn't).
Appreciate your help.
Les
Please right click on your software and go to compatibility mode and select "Windows XP with SP3" in it, click APPLY and OK.
Confirm if the software now send print commands perfectly?
I haven't been able to find a thread that solves my issue yet so opening this one up. I'm trying to install the font but it is giving me an error on install. We would like to use it in a desktop format initially so that document can be passed around internally and edited before putting on our site. I have read it should be good 'our-of-the-box' to install with no issues, however, when trying to install the font this is the error message I get:
"Cannot install FontAwesome.otf
The file '\common.ecamericas...\FontAwesome.otf' does not appear to be a valid font"
This happens for the true type font file as well. Any help would be appreciated so we could hash out which icons we would like to use without all getting in a single room together.
Thanks.
Try to install it with admin or root account