If your read the post I referred to, you can see that I actually filed a bug report in April 2018 for the problem with the smart punctuation. Unfortunately, filing a bug report with Corona is like sending stuff into a black hole, you never hear from it again…
Unless there is a workaround that I do not know of, this together with the Android native text bug are now a showstopper.
There seems to be a way to disable iOS smart punctuation by setting the iOS property smartQuotesType to UITextSmartQuotesTypeNo.
https://pspdfkit.com/blog/2018/ios-11-smart-punctuation/
See the section “Replacing Smart Quotes with Straight Quotes” at the end. Would this be possible to set in Corona somehow? If so, that would at least take care of the iOS part of the problem.
This is the kind of bug that will likely never rise to the level that we will have time to address or fix. You’re trying to use native.newTextField in a way it was not designed for (albeit a popular desired feature). We have to balance this against being able to publish your game to Apple and Google. We have two rapidly approaching deadlines from Google to meet.
Our team is absolutely swamped right now and I can assign this to an engineer, but the chances of it getting worked on is very unlikely.
Back in January, we made the source code open source, hoping the community would get more involved and this is a good feature for a community developer to take up and work on.
Rob
Ok, I understand. I created an issue for this on the GitHub page of Corona, is that the correct way to raise this to the community?
Yes
@carloscosta: first: in many parts of the world, people run their apps on much older devices than both you and I are used to. I want to make sure my apps work for them too. Besides, I just tested it on Android 8 and it does not work there either.
Second: I know there are workarounds but my question was whether this was a bug or not.
Android market share with version less than 4.4 is less than 5%. And that’s all versions combined. And this numbers will go down with time ofc.
If the problem is with android 8 also, that’s new data that was not mention before. But I don’t spend time optimizing my code for 5% of market share. I prefer to spend my time, providing a much better experience to the rest of the 95%. If I can do it for the 100%, ofc I will, but in smartphones, that’s probably impossible. There’s to many makers, variables and screen sizes to make them all happy.
Second: you knew already it was a bug, you just needed the confirmation. I gave you a simple solution for a problem you already knew and corona will not take care, at least for a long time.
The event.numDeleted isn’t correct on Android 7 either so it’s definitely a different behavior on Android than the documentation implies. It’s something that needs looked at.
Rob
I understand that this has a low prio but I am thankful that you will look at it eventually. As previously mentioned, there is also the other bug with the incorrect interpretation of the iOS “smart punctuation” correctly. Maybe that wil also be looked at eventually (bug report filed a year ago).
Anyway, I have found a workaround so I am not stuck anymore… 