Julian

Your help page is a bit unclear and confusing about what is supported. I'm talking about the page here, in particular section 2... https://help.evernote.com/hc/en-us/articles/209125827 At time of writing it says about the different clip types... Article - No mention of any specific browsers so assume this works in Edge Simplified Article - Explicitly lists various browsers. The list does not include Edge so assume this doesn't currently work in Edge? Full Page - No mention of any specific browsers so assume this works in Edge Bookmark - Explicitly lists various browsers. The list does not include Edge so assume this doesn't currently work in Edge? Screenshot - Explicitly lists various browsers. The list does not include Edge so assume this doesn't currently work in Edge? PDF - Doesn't list individual browsers but has a message explicitly stating that this type isn't currently supported in Edge so that's clear Selection - No mention of any specific browsers so assume this works in Edge Custom clips - No mention of any specific browsers so assume this works in Edge I'm hoping my assumption is correct in that, for the types where you don't mention any list of specific browsers, that means it works with all of them including Edge. It is Simplified Article, Bookmark and Screenshot that are particular confusing when taken together with the description for the PDF clip type. The first three don't list Edge as a supported browser so that's worrying, but then again they don't have the explicit Edge-not-currently-supported message that the PDF clip type has so is that all OK then and for the first three it's just a case of someone not updating the previous list of browsers in the help text? I'd appreciate some definite clarification on just what types are supported in Edge at the moment and also suggest that you do some re-wording of that section of the help page to remove the potential confusion over some of the items.

I agree with JM05. I've had a long relationship with Evernote, never quite getting to the stage of using it seriously but every time I come back and have another look it seems to keep getting better and I get ever closer to using it for real. On this topic though I could swear that when I last looked, which might have been a year or so ago, there was at least some basic font and size adjustment capabilities in the iPad client that seems to have been removed. I seem to remember that maybe in the past there was the ability to format something as a heading and maybe sub-heading that gave different font sizes, albeit pre-defined ones. At least for me that was all that I really wanted but even that seems to be gone now (assuming that my memory isn't playing tricks on me about it ever being there in the past or that it is still implemented but I can't see how to access that functionality in the latest iPad client). - Julian

Thanks. I was just curious really. When I first came to EN one of my big issues was some way to implement a proper multi-level hierarchy but I've come up with a new way of organising my data that works for me and removes my need for anything more than a single level tag space so I don't think that I'll even use the single level of stacking when it comes to Windows and iDevices. As jna said though, the fact that "foobar" can't appear under both "foo" and "bar" makes it ugly to implement a proper tag hierarchy even though it is technically possible. The user is left having to disambiguate any tag names that they want to have appear in multiple places in the hierarchy, e.g. "foobar_foo" and "foobar_bar" and the more levels then the worse it can get, e.g. a tag of the form ___ which soon gets very ugly. Allowing the same tag name to appear in multiple places in the tag tree in the UI would be a big step forward. That still leaves people to make sure that, if they tag a note with "foobar", then they also remember to add either the "foo" or the "bar" tag (and any tags for levels in the hierarchy above that) to give the "foobar" tag its full path/context in the hierarchy but at least that's cleaner than forcing tags to be full pathnames as described above. Luckily this isn't an issue for me anymore but I do feel some sympathy for others that still want a full hierarchy. - Julian

Is it possible for a notebook stack to have another stack within it, i.e. is this a single level folder hierarchy or a multi-level structure? - Julian