Jump to content

mwang

Level 2
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

7 Neutral

About mwang

Profile Information

  • Subscription
    PREMIUM

Recent Profile Visitors

3,084 profile views
  1. My sentiment exactly. That, and the fact that Simplified Formatting is still broken after 4 GA releases, are the main reasons why I'm still on v.6.9.2. I just don't know what to expect from Evernote anymore. I no longer have confidence in the release notes, so I wait for feedbacks from early adopters on this forum, and sure enough each time I see things that suggest I should stay away. Not that I'm happy with v.6.9.2, which has many shortcomings. But at least it behaves predictably here.
  2. My fault; I should have mentioned it. No, other things beside the first image are not removed; they are just obscured by the first image, which is indeed "stretched disproportionately" to cover the whole page. Remove the first image, and you'll see, uhh, the 2nd image, also stretched disproportionately to cover the whole page, and so on. The text would be revealed once you remove all the images. The screenshots I gave in the earlier post mentioned above, and the examples in the public folder I set up yesterday, have all gone through the same "pre-processing" in order to show what is wrong with the newest betas. The "stretched images covering the whole page" issue is unique to Guardian, and has been there since as far back as I can remember. I blame Guardian for it, and I've set up a Keyboard Maestro shortcut to make dealing with them easier. The "paragraphs being crammed together without separating lines" issue, on the other hand, is new, starting from 6.10 betas. And it's the one that force me to stay with 6.9.2. It's partially fixed in a later beta, so simplifying a page clipped from the New York Times website, for example, is no longer a problem. The problem nevertheless persists with all pages clipped from the Guardian.
  3. @Johnathan Hebert & @JMichaelTX, thanks for following up. More details can be found in one of my earlier posts (with screenshots): Apologies to Johnathan though, for it's Jason who responded, not Johnathan. I've just set up a public notebook (first time doing this, hope it works as expected) with examples, for anyone who wants to take a look. Please read my description in the post quoted above if you can't see anything wrong.
  4. One regression I've reported many times (starting back with 6.10 beta 3) is still there: The problem of "Applying Simplify Formatting to clipped notes removed returns" hasn't been fully fixed. The issue was at least acknowledged (by Johnathan, IIRC) once, but has never been fixed. Guess I'll have to stay with 6.9.2, again, since it's not even mentioned in the release notes. Sad!
  5. Unfortunately this is still not completely fixed, as reported in beta 4 here. This will be the 2nd major update in a roll that eludes me. Since the introduction of the bug in 6.10 betas, I've been forced to stay with 6.9.2. Sad.
  6. Thanks for looking into this. I'm also using Chrome, but let's first make sure we're talking about the same thing: by "removing returns" I mean blank lines separating paragraphs are removed by Evernote betas (starting from 6.10 betas). Please see the attached screenshots below. The first two are from the same Guardian story (United Airlines defends gate decision ...), with the first one processed in Evernote 6.11B4 and the other processed by 6.92. (steps: one single click into the article, then shft-cmd-F to simplify formatting.) For comparison, a second set of screenshots are provided, clipped from the New York Times (Congress Moves to Overturn ...), again processed in 6.11B4 & 6.92 respectively. As you can see, they are identical. A side note: I don't insist on keeping/adding a blank line between two paragraphs, if Evernote allows changing paragraph spacing (as in Word or Kindle). Thanks!
  7. These two regressions are still there: The problem of "Applying Simplify Formatting to clipped notes removed returns" hasn't been fully fixed. System-wide Show Fonts shortcut missing. More details in my earlier report here. The 2nd issue (missing cmd-T) is particularly puzzling: is that something really difficult to fix?
  8. Thanks for this, but the fix doesn't seem to work universally. For notes clipped from the Guardian website, for example, the problem still exists. For notes clipped from the New York Times, on the other hand, the command works as before (6.9.2). Another bug reported way back (and should be easy to fix) is still here: Recent Evernote for Mac betas (starting from 6.10.x) have removed the system-wide default keyboard shortcut for the "Fonts" dialog (%T). Yes, I know I can fix this myself. But the removal doesn't make sense since you're not assigning the shortcut to something else. (Nor should it be reassigned since it's used the same way across different applications.)
  9. Please don't forget what I reported earlier as well: Thanks!
  10. I do, as I'm back to v.6.9.2. :-) Thanks, I know that. Still, it's a regression with 6.10 betas, so I'm reporting it. Again thanks for the suggestion. That's indeed what I would have to do if the databases were incompatible; dodge the bullet this time, thankfully. Rebuilding the database from scratch is nevertheless very time consuming (did it a few times in the past), and quite disruptive for my work. (Yeah, I can use my notebook or the web version, but that's not quite as efficient.) And that's why I made the request I did.
  11. 3 issues to report: 1. system-wide shortcut for fonts adjustment (%T) no longer works. Earlier versions short "%T" beside the "Show Fonts" command under the "Format" menu, not anymore with 6.10 betas. 2. There is no longer an empty line separating two paragraphs after using Shift-Command-F to simplify formatting. I capture a lot of online news articles and this is a command I use often. Before Evernote allows us to adjust paragraph spacing as in a word processor, I much prefer the old way (a blank line between paragraphs) than having all paragraphs cramped together. Please at least keep it as an option. Please! 3. I tried to go back to version 6.9.2 (due to the previous issue), only to find I couldn't (got the "Version too old" error message). Fortunately I managed to go back after editing the two "version" files in ~/.../com.evernote.Evernote. I hope there's a warning about this before you call upon people to beta test, especially when there's truly incompatible changes and one really can't go back. If there is no incompatible changes, please make it easy for people to go back. Thanks!
  12. Here it does open the Evernote app with Firefox and Safari, though only after opening in the browser first. With Chrome it doesn't work, even after I've enabled the "Open in Evernote for Mac" option in the dialog shown below. That's strange since Chrome has been my default browser for a few weeks, and I should have noticed it if it didn't work with Chrome. It's one of my favorite Evernote features. What browser do you use? Have you ever seen the dialog below?
  13. Hi, I tested out Saferoom for Mac for the first time just now, and ran into a strange issue right away. I duplicated a note, moved it to "Encrypt_Inbox", hit the "Encrypt notes" button (on the Saferoom app), and got an encrypted note. So far so good. I then moved the encrypted note to "Decrypt_Inbox", and hit the "Decrypt notes" button. To my surprise, the result is different from the original note! A side-by-side screenshot is attached below. The difference is too obvious to miss. In fact, all the image inserts in the article have been moved to the end (yes, they are still there thankfully) in the decrypted version. Two more things: the encrypted note is not tagged as "encrypted", nor is the decrypted note tagged as "decrypted" (I remember reading that somewhere, either in this thread or on your website). the url of the original note is missing from the "decrypted" note. (I think it makes sense to strip the information from the encrypted note, but it would be better if such information can be saved in encrypted form and restored when decrypted.) The note I tested with is a news clip from anandtech.com, so I don't mind putting it in a shared notebook if you want to take a look. Let me know. Edit: forgot to say: I tested on OS X 10.11.4, with Evernote v.6.6 (453293 Direct), and Saferoom v.1.6 (166).
  14. Turns out I didn't kill those decade tags cleanly enough. (Long story short: a sleeping notebook had some unsync'ed new/modified notes still tagged with those, and they were sync'ed after I removed those tags from the desktop.) After those tags are truly gone, EN Clipper has stopped suggesting them. It's my own oversight. My apologies.
  15. The "cookies" suggestion is a nice thought. Cleaned my Chrome cookies (and cache/history and every thing else I can purge from the preferences) and still got the same result, unfortunately. I even tried starting both Firefox and Chrome with a new (empty) profile and still got the same result. So I guess it's something associated with my account in the Cloud. It's still odd even if that's the case, however, considering that the particular tag had been renamed twice a few weeks before being eliminated: from "2000s" to "decade.2000" and then "dec.2000". With each rename (done in the standalone client) the EN Clipper picked up the new term as soon as the change was sync'ed to the cloud. That suggests the Clipper is working with "live" tag dataset (what's actually in my database) instead of working from "experience" (what I choose to tag when using the Clipper), doesn't it? In addition, even if the Clipper is learning from my past input, it should not suggest "dec.2000" either since, as I said, the tag is for old news published in the last decade. As I was slowly moving from Devonthink to Evernote over the last full months, almost all new clips I've made are current news, so I almost never manually tag anything with "dec.2000". It's another hint that EN is basing its tag suggestions with the actual tagging system in my database (wherein a large portion of notes were tagged with "dec.2000"). It therefore puzzling that it's not picking up the fact that a tag is no longer alive. Hope, as you suggest, EN Clipper would eventually "learn". In fact, that's why I waited for a week before asking. Guess I'll just have to wait longer. Thank you for trying to help anyway.
×
×
  • Create New...