Jump to content
Due to limited holiday staffing, chat will be unavailable from Thursday, July 2 at 5:30 PM (CDT) to Monday, July 13 at 8 AM (CDT). This will allow us to reply to your email requests as quickly as possible. Thank you for understanding. ×

Johnathan Hebert

Evernote Staff
  • Content Count

    212
  • Joined

  • Last visited

  • Days Won

    3

Everything posted by Johnathan Hebert

  1. I can tell you that the final editor build has been included with the app, but I cannot account for external factors like the app store, etc. It is the next release going out the door for iOS as far as I know. Please keep in mind there are many millions of users and many issues that require attention, planning, prioritizing, etc -- we are working as hard as we can to address them in a way that is most valuable to our users. In general, making substantial improvements to the editor is in natural tension with preserving all legacy behaviors and quirks that have existed for the life of Evernote. As I briefly explained before, the adjustment of the ENML was done to fix a class of editing bugs. It was never intended to have a visual or behavioral effect, which is why it is being reverted. In short, it usually is never a quick fix, but more of a quick trade-off.
  2. We are aware of the issue. As I have mentioned in the other post, this fix will be included in both the 8.2.2 GA release on iOS, and the 6.11.1 release on Mac.
  3. Hi @Chad CEO, I was able to include the changes, so it will be fixed in the upcoming 8.2.2 GA release. Just so I understand you correctly -- you are saying that it is not possible for you to use the app because an extra line is appearing in double spaced content? Can you clarify why you cannot use the mobile app? The extra line is preventing you from using the app? Or is there some other error or bug that is going on that stops you from using the app?
  4. No plans at the moment, but you can right click and open in the default application. I'll ask around internally just to be sure.
  5. Thanks for mentioning. We do know about this and it has been fixed and will be in the Beta 2 release.
  6. Just to be sure, when you mentioned pasting your "spreadsheet clips" -- can you be more specific or attach some examples? I'm not sure about the other issues yet, but if I get more info I can respond here.
  7. I believe the underlying cause of this issue has been fixed internally, and will be available in the Beta 2
  8. Thanks, we are aware of this one. It's something that may have to be come in the next release because of the nature of the problem.
  9. Thanks, I worked with Alexander and Jeff to get the ENEX, and spent some time looking into this. It helped us find a problem with the rendering of tables. I am trying to get the fix in for the 6.11.1 GA, thank you!
  10. Thanks for the suggestion. We are indeed looking into this. The recent editor changes, the restructuring of the underlying ENML, etc, are being done to enable more advanced and delightful things like the features you mentioned.
  11. Thanks. I also need to correct what I said about the schedule/release earlier: I am working to get this fix in for the 8.2.2 release, but if it does not make it in time, it will be in the next iOS release. It will also be carried to the Mac/Win releases coming up as soon as we can get it in. It is working in internal builds.
  12. I just wanted to clarify one thing. When you say "double spacing", are you talking about double spacing within a paragraph, or spacing between paragraphs? The change we are making will do this: If you just have a single paragraph, but it is long enough to wrap across several lines, those lines will not be double spaced. But if you then add a second paragraph (by pressing the enter key), there will be a space between the two paragraphs.
  13. Thanks for the example -- this is now fixed and will be in the 6.6 Beta 2
  14. Hi @Chad CEO -- In the next beta of 8.2.2, or the GA, you should see all formatting, spacing, etc retained on pasted content, and the extra editable line should not be there. In other words, the original behavior should be restored.
  15. @JohnLongney I understand you are having problems printing the background colors on table cells -- we are working on this issue.
  16. Can you provide some more details and example steps of how to reproduce the problem. I'm sorry, but I cannot understand exactly what is being described here.
  17. Thanks for mentioning this -- can you post a screenshot or a sample ENEX file so we can take a look at the problem?
  18. I think I know what might be going on here. Those tables were probably there all along because they existed in the HTML where you copied them from, but they had formatting that made the table structure invisible. With these new table enhancements in this release, the note editor is preparing those table for more advanced editing. In this case, you probably don't need that advanced table editing on these single cell tables. We try to identify tables that are likely to be content that users want to edit as tabular sets of information, as opposed to tables that are used for purely layout and positioning purposes. I'm not sure what the best way to handle a situation like this -- can you provide the location where this content was copied from?
  19. I replied to this in a few other places, but wanted to clarify again. This is to allow the table row headers and dots to appear to the left of the table when your keyboard cursor is in the table, while at the same time aligning the left edge of the table to the left edge of surrounding paragraphs. Otherwise, the table row controls would not be visible, or the table would have to "jump" when you start editing it, or the controls would have to be less advanced, or more compressed, etc... this is the current thinking. What do you suggest?
  20. This is to allow the table row headers and dots to appear to the left of the table when your keyboard cursor is in the table, while at the same time aligning the left edge of the table to the left edge of surrounding paragraphs. Otherwise, the table row controls would not be visible, or the table would have to "jump" when you start editing it, or the controls would have to be less advanced, or more compressed, etc... this is the current thinking. I'm not sure what you mean here -- what is the desired behavior? And what exactly is it doing?
  21. Thank you for this example, I am looking into it -- did you have more examples?
×
×
  • Create New...