Forum Replies Created
I could not reproduce in 20.5.6. I understand it doesn’t happen all the time. I recommend setting your PLSQL file extension to .pls. That should make it easier for you and for programs to recognize the SQL type.
Yutaka, they want to color just the left margin of the view, also known as the gutter. They tried to do it by changing the background color of the outline part. Only “text color” has an effect on outline. As far as I know, you cannot set a separate color for just the outline or gutter. Am I correct on that?
ArthurZ, can you confirm if I understood you correctly? You created a new MySQL file and a PLSQL file and saved them both with a .sql extension. You switched to the MySQL file, then created a new PLSQL file. The previous MySQL document changed to PLSQL configuration.
Could you tell us your EmEditor version from the About EmEditor dialog?
I updated the script to avoid capitalizing a character proceeding an apostrophe: https://gist.github.com/MakotoE/d74d75ade47f57c1c9396488bada8347June 21, 2018 at 11:11 am in reply to: Auto replacement from CJK Compatibility Ideographs to CJK Unified Ideographs #23459
I see; then using the flag
document.selection.Find()to search all open documents is the method to use, as you used, or in Uni_CJK_2.jsee. EmEditor does freeze when processing large documents, but it is working. If you have enough memory available in your system, turning off “Use Temporary File to Reduce Memory Usage” in Tools > Customize… > Advanced will decrease search time. When you start the script I recommend waiting for a couple hours, then come back to see if it finished.June 20, 2018 at 2:18 pm in reply to: Auto replacement from CJK Compatibility Ideographs to CJK Unified Ideographs #23448
I’m not exactly sure how you want to input the list of documents. I’m afraid there is no method to get a list of documents in a folder, but what you can do in File Explorer is to highlight multiple files, hold shift, right click, and select “copy as path” to get a list of documents that you can put into the script. The scripting language is designed to be simple, so it is not able to show a graphical interface.June 19, 2018 at 12:57 pm in reply to: Auto replacement from CJK Compatibility Ideographs to CJK Unified Ideographs #23441
Yutaka says that CJK compatibility character replacement is not planned for the near future, although he does understand that it would be useful for the Korean language.
I did revise your macro to do this, and without freezing for multiple documents, hopefully.
Your macro works fine, but I did make some changes to make it easier to maintain, if you need to modify it later on. In Uni_CJK_2.jsee, I create a list for the conversion pairs, and loop though it. Unicode characters can be written like “\u0000” if that is useful.
To fix the issue you had with the macro not able to process multiple files, Uni_CJK_3.jsee fixes this by opening one document at a time. It saves and closes the document when the script is finished with the document. I think it was a memory issue, so if that was the case, this should work.
If you know the Unicode value for the IVS character, you can input them via Insert Special Character dialog (ctrl-shift-I).
Thank you for your input. There will be preceding 0’s for the character values in the next build.
The “0x” is there to distinguish the character code values from the other numbers that appear on the status bar.
CP936 is now implemented for the next build. The status bar field only expands, and resets size when changing documents. This is because when the field was resized every time the caret changed position, it was hard to read the values.
LTT, encodings that the character code dialog have not implemented left the status bar character value blank. For example, UTF-7 is not implemented, so the character code value is blank. I have changed it so that if the encoding isn’t implemented yet, and the status bar would be blank, the Unicode value appears instead.
When you first found that the character code value is blank inside the status bar, (link to comment) which encoding where you using? I may implement this encoding if it is well used.
Thank you, this has been fixed for the next build.
We appreciate your feedback. Although we won’t be implementing this feature in the near future, I did make a script that can do this: https://pastebin.com/yHZYnLMV.
excludeWordsis a list of strings that are not matched when converting words to sentence case. Just save the script as a .jsee file and add the macro in the Customize Macros window. The words that start inside the selection are converted to sentence case when the script is run. It’s not exactly fully tested, so let me know if it’s not working.
Thank you sky. I have fixed this for the next build.
On beta 2, emed64_17.5.902_portable, I am seeing the correct output for various three byte CJK characters. I tested on UTF-16 and UTF-8. Could you show me a screenshot of what you are seeing?
Thank you for your feedback. The Character Code Value window was intended to show the Unicode block name if character name was not found. The next beta version will correctly display the block name.