TODO

• Update emoji list https://unicode.org/emoji/charts/full-emoji-list.html
• Multiple code points
• Text to emoji https://meowni.ca/emoji-translate/
• Image to emoji https://github.com/notwaldorf/emojillate

Read more

• http://apps.timwhitlock.info/emoji/tables/unicode
• http://www.unicode.org/emoji/charts/emoji-zwj-sequences.html
• https://oleb.net/blog/2016/12/emoji-4-0/
• http://crunchybagel.com/using-emoji-skin-tone-modifiers-in-swift/
• https://oleb.net/blog/2017/11/swift-4-strings/

Consider 👩🏻‍❤️‍💋‍👨🏼, which is formed of

• 👩 (woman)
• Light Skin Tone
• ZERO WIDTH JOINER
• HEAVY BLACK HEART
• VARIATION SELECTOR-16
• ZERO WIDTH JOINER
• 💋 (kiss mark)
• ZERO WIDTH JOINER
• 👨 (man)
• Medium-light Skin Tone

If I do

Smile.unmodify(emoji: "👩🏻‍❤️‍💋‍👨🏼")

Everything except the 👩 is removed. This completely changes the meaning of the emoji, which I don't think unmodify is supposed to do. I had expected 👩‍❤️‍💋‍👨 instead. Is this intentional?

See: https://blog.emojipedia.org/ios-11-1-emoji-changelog/

// swift-tools-version:5.1
// The swift-tools-version declares the minimum version of Swift required to build this package.

import PackageDescription

let package = Package(
name: "Smile",
platforms: [
.macOS(.v10_15),
],
products: [
// Products define the executables and libraries produced by a package, and make them visible to other packages.
.library(
name: "Smile",
targets: ["Smile"]),
],
dependencies: [
// Dependencies declare other packages that this package depends on.
// .package(url: /* package url */, from: "1.0.0"),
],
targets: [
// Targets are the basic building blocks of a package. A target can define a module or a test suite.
// Targets can depend on other targets in this package, and on products in packages which this package depends on.
.target(
name: "Smile",
dependencies: [],
path: "./Sources/"),
.testTarget(
name: "SmileTests",
dependencies: ["Smile"],
path: "./SmileTests/"),
]
)

For example: ⏰⌛️💳🆙...

I suggest to update switch:

switch value {
        case 0x1F600...0x1F64F,
             0x1F300...0x1F5FF,
             0x1F680...0x1F6FF,
             0x1F1E6...0x1F1FF,
             0x2600...0x26FF,
             0x2700...0x27BF,
             0xFE00...0xFE0F,
             0x1F900...0x1F9FF,
             65024...65039,
             8400...8447,
             9100...9300,
             127000...127600:
            return true
        default:
            return false
        }

We need to upgrade demo Swift version, because new Xcode does not support the lower Swift version.

$ cd Example/SmileDemo/
$ pod install
Analyzing dependencies
Fetching podspec for `Smile` from `../../`
Downloading dependencies
Installing Smile (1.3.1)
[!] Unable to determine Swift version for the following pods:

- `Smile` does not specify a Swift version and none of the targets (`SmileDemo`) integrating it have the `SWIFT_VERSION` attribute set. Please contact the author or set the `SWIFT_VERSION` attribute in at least one of the targets that integrate this pod.

Since there is no active development on this repository since Nov 2018 (that's when 2.0.0 came out as a Pod) and no newer versions are released, I believe it is your duty to make it clear in the README.md that this repository is not actively maintained and people should steer clear of it. We have this repository as a dependency and now we have to do a lot of work to get rid of it. Thank you.

I did the pod install and I am getting

import Smile

Smile.isEmojiOnly(message.value)

Module 'Smile' has no member 'isEmojiOnly'

When using smile to detect emoji for "*" it returns that there is an emoji present.

There is a strange behavior where the man_juggling from the emojiCategories isn't recognized as an emoji using isEmoji and doesn't any values in the emojiList when I do a CTRL-F in Xcode, even though it's very clearly there in the emojiList if I look visually.

I'm not sure exactly what's wrong or how far it extends to other emoji, but it definitely seems like something isn't right.

The pod is taking too long to build after upgrading to Swift 5. From the output below it takes about 20 minutes and this is just the best case. It takes longer than that sometimes.

[23:33:54]: ▸ Processing Smile-Info.plist
[23:33:54]: ▸ Copying Smile-umbrella.h
[23:53:05]: ▸ Compiling Smile_vers.c
[23:53:05]: ▸ Compiling Smile-dummy.m
[23:53:06]: ▸ Compiling Smile_vers.c
[23:53:06]: ▸ Compiling Smile-dummy.m
[23:53:06]: ▸ Linking Smile
[23:53:06]: ▸ Linking Smile
[23:53:06]: ▸ Generating 'Smile.framework.dSYM'
[23:53:06]: ▸ Touching Smile.framework

Seems like the Smile.containsEmoji function thinks Digits are emojis. Could you please fix that? :-)

http://www.iemoji.com/view/emoji/1025/new/desktop-computer

🖥
U+1F5A5

I have tried several alternate style emojis and they are all returning false in isEmoji. I tried several and any alternate styles I tried would return false. A couple I know I tried are 🤴🏻, 🦹🏻‍♀️

It seems like just appending a skin tone modifier from Smile.Sequence.SkinTone does not work for all emojis, so how do I know when to do this?

Some emoji are in the Emoji.swift but missing from the categories, for example, 🤩(starstruck)