Thanks! MINDBLOWN :O :O :O

@Guido-Brinkman

And please search for this first in the reported bugs, before creating a new one. I’m sure it already exists…and you can add any new info to an existing issue if you think it is deficient.

@Terry-R said:

? *| *(.+?) *|,| *[.+?] *|:

Thank you very much Terry-R. Worked perfectly.

I’ve tested 10 lists and everything is as I wanted it to be.

Thank you again.

Claudio

Hello, @tokiedian-steelpanthers,

Your default Noto Mono font does not reproduce the glyphs of the Unicode IPA Extensions block characters, below :

http://www.unicode.org/charts/PDF/U0250.pdf

Here are, below, a table with a summary of some monospaced fonts, which represent all IPA extensions characters, properly

For the record, you may, also, refer to :

The two MS Mincho and MS Gothic fonts, which can handle the Japanese Hiragana and Katakata characters

The proportional  fonts Lucida Sans Unicode and Microsoft Sans Serif, which both support the IPA Extensions characters, too

•----------------------•-----------•--------•---------•-------•-------------------------------------------------------------------------------------------------------• | Font Name | Version | Glyphs | Digit 0 | Serif | Download link | •----------------------•-----------•--------•---------•-------•-------------------------------------------------------------------------------------------------------• | Code New Roman | 2.10 | 2,740 | Slashed | | http://www.fontspace.com/download/21129/7aaebf327a7240b98dabadef5d1bc786/typostyle_code-new-roman.zip | | Consola Mono | 2.001 | 1,465 | Slashed | | https://fontlibrary.org/assets/downloads/consolamono/61cc2afcc4eca96efe7c6ebf178d39df/consolamono.zip | | Cousine | 1.20 | 2,385 | Dotted | | https://www.fontsquirrel.com/fonts/download/cousine | | DET Terminal Modern | 1.0 | 2,218 | | | https://dl.dafont.com/dl/?f=dec_terminal_modern | | DejaVu Sans Mono | 2.37 | 3,377 | Dotted | | http://sourceforge.net/projects/dejavu/files/dejavu/2.37/dejavu-fonts-ttf-2.37.zip | | Espresso Mono | 2.17 | 2,870 | Slashed | | https://github.com/jmazzi/dotfiles/tree/master/.fonts | | FreeMono | 0412 2268 | 4,177 | | Yes | http://ftp.gnu.org/gnu/freefont/freefont-ttf-20120503.zip | | Iosevka | 2.0.0 | 3,712 | Slashed | | https://github.com/be5invis/Iosevka/releases | | Iosevka Slab | 2.0.0 | 3,712 | Slashed | Yes | https://github.com/be5invis/Iosevka/releases | | Meslo LG M | 1.210 | 2,708 | Slashed | | https://github.com/andreberg/Meslo-Font/archive/master.zip | | Meslo LG S | 1.210 | 2,708 | Slashed | | https://github.com/andreberg/Meslo-Font/archive/master.zip | | Meslo LG M DZ | 1.210 | 2,708 | Dotted | | https://github.com/andreberg/Meslo-Font/archive/master.zip | | Meslo LG S DZ | 1.210 | 2,708 | Dotted | | https://github.com/andreberg/Meslo-Font/archive/master.zip | •----------------------•-----------•--------•---------•-------•-------------------------------------------------------------------------------------------------------• | MS Gothic | 5.10 | 22,290 | | | | | MS Mincho | 5.10 | 19,398 | | Yes | | •----------------------•-----------•--------•---------•-------•-------------------------------------------------------------------------------------------------------• | Lucida Sans Unicode | 5.00 | 1,779 | | | | | Microsoft Sans Serif | 5.11 | 3,205 | | | | •----------------------•-----------•--------•---------•-------•-------------------------------------------------------------------------------------------------------•

Cheers,

guy038

What are large files in you case? At least the 64 bit version of N++ should do better on that compared to the 32bit one.

See also https://github.com/notepad-plus-plus/notepad-plus-plus/issues/681

@Bill-L

I think you are asking in the wrong place, but a wild-guess might be the type of line-ending characters you are using…

I guess you use Notepad++ with a russian locale. This locale has the known problem that the menu entries regarding UTF-8 in the Encoding menu are not in sync with the encoding indicator in the status bar of Notepad++.

UTF-8 without BOM:

In the Encoding menu (translated): Encode in UTF-8 without BOM In the status bar: UTF-8

UTF-8 with BOM:

In the Encoding menu (translated): Encode in UTF-8 In the status bar: UTF-8-BOM

A fix is on its way and will be part of the next release, see here.

As a temporary workaround you could integrate the patch above manually into your russian.xml file. You can find this file in <Installation-Path-of-Notepad++>\localization.

After you did that there are 2 possible ways to activate the changed language file:

Start Notepad++, switch to an arbitrary language and then back to russian again. Copy the changed russian.xml file to C:\Users\<Username>\AppData\Roaming\Notepad++ and rename it to nativeLang.xml.

Please note: You have to follow only one of the two steps above!

@Shanmuga-Velu
This is a possible method to help you overcome the issue of requiring line numbers in the selected print jobs.

Notepad++ provides the ability to insert numbers in any column of the file that is opened. So if you were to select the first row and the first column and click the mouse so it shows a flashing cursor there. Then use the Column Editor (Alt and C keys). Use “number to insert”, start with 1 (if you want line 1 to show as 1), increase by 1 and may I also suggest tick the “leading zeros” (so all lines align). Have “Dec” selected and click OK.

So now every line in the file with have the line number inserted into the start of every row.

Now you can easily remove the lines you don’t wish to print. The result will be lines with the line number at the start. If you need to pretty the lines a bit, perhaps a space between the number and the text use the column editor to insert a space first, then do the number insert afterwards.

Terry

Hi @terry-r, @devin-rusty, and All,

If we assume that there is always, at least ONE pure blank line, between the CONTEXT: block of lines and the statement > END STRING, an other formulation of your regex S/R could be :

SEARCH (?s-i)^(> BEGIN STRING\R)(.+?)(> CONTEXT:.+?\R)(\R)+

REPLACE \1\4\3\2

Cheers,

guy038

P.S. :

Actually, the syntax (> CONTEXT:.+?\R)(\R)+ is equivalent to (> CONTEXT:.+?)(\R){2,}. In other words, it searches for the string > CONTEXT: followed with the shortest range of any character till, at least, two consecutive line-breaks. But, with the later syntax, the range of characters (> CONTENT:........) does not include its final line-break !