Did this post help you? If so, please give it a Like below.
Still stuck? Ask me a question!
Tips & Tricks Find new ways to stay in flow or share your tips on how you work smarter with Dropbox.
You'd have to license the font, as fonts are a bit like software. If you used another grotesk font that you already have (many people have Helvetica for example, which is a grotesk), then you'll get something similar.
I saw that somewhere on the web and I downloaded that font and it doesn't seem to be the same one...super close, but not the same. I just thought I'd try to see what the name of it was or if they were willing to tell me
Myriad Pro is very, very close to the official Splunk branding font. But acharlieh's point is important: if you are creating something that will look like Splunk branding and will be distributed beyond the personal hobby level, you should proceed with caution, because Splunk branding belongs to Splunk.
Looking at a Splunk 6.0.6 installation that I have handy, inspecting the "logo" on the front page you can see that it is in fact text, with a font family of "Splunk Icons" which happens to be served up at /en-US/static/fonts/splunkicons-regular-webfont.woff
Looking at this font, it looks like a base font was taken, and glyphs are overridden to give what is needed, and it doesn't really seem to be a unified font at all. (at least the splunk letters are different than the base font as you can see here):
Now the other font that is embedded in the page and seems to be the font used most other places is called Roboto. Maybe using this font might give you some of the style that you're looking for? Or you could try running the logo through something like What the Font! and see if you could get another approximation.
Edit to add: Do be careful in designing your newsletter. While we all love Splunk, and want to show how cool it is, your newsletter should be abundantly clear at a glance that you're a Splunk Enthusiast and not an employee of nor representing Splunk, Inc. themselves. IANAL but the more the line is blurred here the more trouble and headaches you might risk.
I am trying to get my emails consistent across all devices (Macbook using Apple Mail, iPhone using Mail, and Windows PC using Outlook). As the iPhone's app is the only one that doesn't let you change the font, I was hoping I could find out which one it is so I can change the other two clients to match it instead.
Yes I am trying to control what my recipient sees, in the sense that I want them to be seeing emails in the same font regardless of which client I use to send (such that I can email from anywhere I happen to be, without worrying about inconsistencies).
This why there is a huge market for outbound mail services that use HTML (in another app/client, not native iOS Mail) to render their messages and even then, include a link that says... "can't see this message... click here..." to be taken to a website that has their message including their HTML formatting in place.
Ok, I think I.may just have one tough cookie. After testing like 30 form apps it cMs down to 2. Jotform.and Typeform. It really was tough because the fact is for the price no form app does even half of what Jotform can do yet I decided to pay more with Typeform..why? It makes no logical sence. I chose it because of..the appearance or primary font Typeform. Uses. It defines the brand and makes things things soothing to look at. Now all they new to do is relate some native inbox or spreadsheet or native app to view form submitting. It is a little off that aftwr being so excited building a form,that I have to the pay Zapier simply to connect to a app that I can actually.use productivly. That's a different post and the genious that designed the corporate Visual identity of Jotform which included colors,shapes and fonts..the top question I have is? What is the fonts name? Sure we can use.google fonts, etc by what is that magic font. I work for one of the busiest restaurant chains in the US and we have a killer and stupid expensive, free to us primary font that I love and defines our brand. So Mr.typeform community. What is your font called!
I often have very limited space when creating reports and dashboards for users. I usually use Arial, or Arial Narrow, but UI isn't my area of expertise, so I want to know, how do you determine an optimal font for fitting the most readable text in the smallest space?
I did a rudimentary by creating a program that iterated through all of the available fonts I had installed on my Windows box at the time and printed a line containing each printable ascii character on to the screen in each of these font's. I repeated the test as well with different font sizes.
The results as I recall them were that Segoe UI and Tahoma were the best with respect to space utilization and readability for UI purposes at 10pt and 9pt sizes. In the short term we settled on Tahoma since Segoe UI isn't freely available for operating systems below Windows Vista. If you don't need to support Windows XP or older an Windows OS or other a non Windows OS then I would definitely go with Segoe UI otherwise I would go with Tahoma if it's available and if all else fails try Verdana. See this list for a lineup of available Windows fonts as well as information about the best of use of each.
Keep in mind as well that starting with Windows Vista I believe, Microsoft now recommends using a 9pt font instead of a 10pt font for UI elements since the Sego UI font displays much clearer than other fonts at low resolutions especially on flat panel displays.
Depending on what platform you are developing for, you may also want to look at modifying font metrics if possible. In .NET with WPF I recall there being quite a bit of ways to modify how the text is rendered to allow for condensing the space between characters and to make the individual characters more narrow. Using this type of technique you can stick with whatever font you like and just tweak it's rendering to get the results you need.
With regard to your specific example graph that you provided: for this particular graph I would recommend pivoting it so the text most likely to be read is horizontal for more natural reading. I would also place the number so that it is inside the each bar of the bar graph when it will fit with a color that stands out against whatever background color is there thus increasing the space for other things such as the labels. Laying out the bar graph as rows would make it easier to read and also to print on multiple pages if necessary. If a row layout is not possible then creating a separate key for each item in the graph would probably be reasonable and that way each bar could be place closer together as well to save space. The key would allow each bar to be labeled such as A, B, C... or 01, 02, 03... for example and the key (layed out in rows somewhere else) would give more detailed information about each.
Remember, a chart or diagram is mainly useful for getting quick visual information. If it becomes too much of a burden to the user/reader your probably best off simplifying it, consolidating some of the details of the chart, or just provide more raw data in a more tabular form.
Update: I've added another comparison below which shows a more complete listing of common characters including capital and lower case letters in each of the previously mentioned fonts with the addition of Verdana and MS Sans Serif (default UI font in Windows prior to Windows 2000). Unfortunately and in response to bobsoap's recommendation for using Verdana, it is pretty clear that Verdana is about the worst compared to the other fonts at 9pt although keep in mind that this may not hold true for other point sizes. Also size isn't necessarily always the most important detail, sometimes it's more important that a font is readable at small sizes than whether it is more compact relative to another font.
Generally, there's an "other way". The answers to this question are all great, but honestly, you should look at all the different option. Squeezing as much text in as little space as possible always means you've botched a previous design choice.
There are so many options, make sure you use the right one. Squeezing as much information into a single small area as possible is always the wrong way to go. Information needs space to breathe, to be readable, to be scannable and recognizable.
Yes, this generally means using way more space. But that's not a bad thing. It will take less effort for the person who consumes the data to quickly scan a couple of pages filled with well-structured information, than to figure out what that one bar means on that one-page-report. Think of the old board member, pocketing his reading glasses while passing the paper to the person next to him: "I can't read this - what does it say?"
There are assumptions in this question, the biggest one being that the "correct solution" to this UX issue is small text. But it's not. Small text becomes unreadable, an issue aggravated by tablets and other mobile devices. What if your user has bad eyesight? What if it's shown on an older, lower resolution monitor? What if there's glare from the sun or a light? So many reasons why small text can be unreadable.
Sometimes a smaller font is a good way out of a tight spot. In this particular case, at least for the part of the problem shown, there is a better solution which is both clearer, and takes half the space, like so:
Many fonts have been explicitly designed for use on computer screens (generally referred to as screen fonts). Matthew Carter's set of typefaces; Verdana, Tahoma, Georgia et al are great examples; they were designed from the outset with the pixel grid in mind. That makes them inherently good for use at smaller sizes (but generally makes them look a bit awkward in print).
93ddb68554