cartographer | provides real-time simultaneous localization | Robotics library

I solved this by using the windows-1252 module to encode the original text and then decoded it using the iconv-lite module.

There is no technical definition of what an "emoji" is. Various glyphs may be used to render printable characters, symbols, control characters and the like. What seems like an "emoji" to you may be part of normal script to others.

What you probably want to do is to look at the Unicode category of each character and filter out various categories. While this does not solve the "emoji"-definition-problem per se, you get much better control over what you are actually doing without removing, for example, literally all characters of languages spoken by 2/3 of the planet.

Instead of filtering out certain categories, you may filter everything except the lower- and uppercase letters (and numbers). However, be aware that ꙭ is not "the googly eyes emoji" but the CYRILLIC SMALL LETTER DOUBLE MONOCULAR O, which is a normal lowercase letter to millions of people.

For example:

When you erase the points from the path you are doing so by copying them to a new path, excluding the ones you want to erase. But you are not also copying the corresponding point type information from the first path; instead you are resetting all the point types to 1, for whatever reason. This loses the information about where each figure within the path starts. So what happens is the new path sees one long connected figure, which explains what you are seeing.
If you want to erase the first n points from the path, you might try something like this instead:

This has nothing with the -A option: modified content, untracked content means those folders are submodules.

Those sub-repos includes files which are either untracked, or modified.

You would need to:

• go into those directories,
• add and commit there, (and push to their respective remote, assuming those changes must be contributes back to their upstream repos),
• then go back to the parent repo, add and commit again in order to record the new gitlink (special entry in the parent index, recording the new SHA1 of those submodules)

But if those changes are purely local and can be ignored (meaning anyone cloning again your repo with you current changes would still be able to make your program work without any of the changes in the submodules), then you can ignore the git status output.