English To Hindi Font Name

[Ahmend Studioz]

To identify a font from an image, use a font finder or font identifier. These tools are great for finding the name of a font or similar alternatives. All you need to do is upload an image of the text by having it readily available on your device or taking a photo.

Yes, WhatTheFont is a simple and easy font finder that can help you identify fonts. Just upload an image of the font you need identified, and the tool will do the job for you. WhatTheFont works by searching through its database and comparing its fonts to the one in your image. The app will list all font matches and give you a preview of how each looks like as text. Enter your own text and play with font size for the full experience. WhatTheFont is available for both iOS and Android devices.

And opening a compiled font file in Glyphs is reverse-engineering including some guesswork, so that is not a good idea for verifying fonts. The process I described above is hard to reverse, because it is not reliably possible to tell which part of the family name was originally meant as style name. For inspecting compiled fonts, I suggest tools like OTMaster, Font Table Viewer, or online tools like FontDrop.

One issue with putting the internal company font code as a prefix is that the styles for that family will be scattered all throughout the font list. We already had that problem with a bunch of Font Company fonts that always put a letter in front of the name from the style. For instance Avant Garde Condensed Bold would actually show up as BCAVGarde in the list.

Adding the suffix to the style name messes up the style linking and compatibility between apps (if you open a formatted document in different apps, the font selection may be different). And you end up with two very similar styles in the family. The can confuse the user.

On the contrary, you may run into legal issues because if you create modified versions of the font, the license usually stipulates that the family name must be different. It is probably best to double check in the original font EULA.

I talked to one of the other graphic designers here and we decided to compromise by putting the font code at the end of the font family name as suggested. It will make the font list pull down longer, but at least the code will be part of the font name.

If you are on a Mac or Linux, simply run this script from the command line in the directory where you have your custom fonts (uses the fc-scan utility from fontconfig which is probaly already installed, but if not you can install it via homebrew: brew install fontconfig):

The script above will run through all the .ttf and .otf files in the current directory, then print out the PostScript Name for each font which you can use to reference the font file in XCode or elsewhere.

This is a bit faster than copy-pasting code inside of your AppDelegate.m file to print out the names every time you want to add a new font file, which is the popular method, and it's also faster than opening the Font in FontBook to inspect the PostScript Name.

USEFUL TIP: If you alias the above script in your terminal so that all you need to do is type a single command to get all the PostScript font names for all the files in the current directory (my function is called fontnames so all I have to do is type fontnames at the terminal inside the directory with fonts in it, and the PostScript names will be printed automatically, then you will save time in your development workflow and have this handy script ready to use when you need it.

After you've added your fonts to your project/app, add this code (probably just in app delegate didFinishLaunchingWithOptions method) in order to print out all the available fonts for your app. From with-in that list you should be able to identify the font you're after. Don't forget to remove the unnecessary code after.

Another "quick, practical" hack that doesn't involve scanning through all the default fonts that exist on either the emulator or device is to use the font for something in your storyboard. Then if you edit the storyboard with a text editor (open as source code), you can see the fonts used with "internal" names if you search for the "customFonts" tag:

Hi there!
I've been using google fonts not only for digital but also print usecases. I've never had any issues with it, when exporting a PDF/X-3 out i.e. of illustrator for print.
Now I have a print product which does have some visual problems with the fonts. I have not converted the fonts into vector paths as I thought, they are going to be embedded anyways.
Unfortunately now I've realised, that the PDF does contain embedded fonts BUT the "wrong" typefaces - or it is missing some. The preflight is giving an alert named: "font name is not unique".
I went through all older PDF-files that I've created the past years with google fonts in it and they ALL have this alert showing up when I do the preflight. There were never any problems with the final print product, so this is the first time it seemed to really making trouble. I am in shock as I didn't know that this can happen... I didn't know there were some fonts that are not able to be embedded properly - and that it is google fonts, that seem to have this issue. Does anyone know this problem (I couldn't really find any problems reported)? Does anyone know how to "rename" the fonts properly? Is there any preflight-fix for this?
Thanks for replies!

I've just realized: Could that be because the font is a "various (VAR) font"? So the font is always named after the "first" one of the possible ones that are listed in the preset-styles? That might be an explanation. I then will never be sure that the PDF has the right "info" about the typeface for the printer in it, as it has simply any name.

Is there a quick way to find the file names of fonts used in a drawing, ie ****.shx or ****.ttf? I get the occasional error message about a missing SHX file but it doesn't seem to give me the option of finding out what a missing file is actually named. That way I could contact whoever sent me the file with the missing SHX file and tell them exactly the additional file to send me.

Our company uses Lucinda Sans as our standard font and I found that it wasn't showing up when working from home. When looking through a true type font directory I found LSANS.ttf and when I copied it to my AutoCAD font directory at home the font showed correctly. It seems that AutoCAD is still using 8.3 file naming convention for font files so matching font names with file names takes guesswork.

In a similar situation if I have a missing XREF I can hover over the saved path and it will give me the name of the the DWG file that is missing. Similar thing with missing color tables where it will tell me the file name of the CTB file. I have found no such thing with fonts.

Another way for fonts is easy done by command _STYLE ... there you have on the left side the list of text styles defined in the drawing, select each of the styles to see if the field "Font Name" shows a yellow warning marker, if so that file is not found.

I'll have to disagree on the first statement. I don't think I have ever seen it tell me what the actual missing file name is when I select the "specify replacement SHX file" option. It is not showing any filename on AutoCAD LT 2018 for Mac here at home and I don't remember seeing it on AutoCAD 2016 for Windows at work. I just indicates that 1 file is missing. I'll check again on Monday.

I did play with the STYLE and _STYLE. I did find a font SHX file that had the yellow warning and was able to install that file. After relaunching AutoCAD I see that there are no longer any yellow warnings on fonts but I still get the missing SHX file warning when opening. Maybe my problem is the line type with symbols problem that you mentioned.

Thanks for the video. I seem to remember that when I tried the "specify missing SHX file" before the file listed in the dialog was one that I had but it kept bouncing me back every time I selected it and tried to open it.

I am always upset when I see this small font of usernames.
When there are many participants at the conference with such a small font size, I have to strain my eyes and spend precious time to understand what name is written on a particular participant.

This is very much needed. The small type size of the participant names is far too small for those with vision problems, and I have yet to find any way to make the names bigger. The option does not exist in Accessibility.

Getting the flexibility to increase the font size for the names of the participants, especially for a premium account who is using ZOOM daily and on multiple screens would be a life saver
Thank you ZOOM Development Team - WAITING for this change

My problem is, since updating Mac to Ventura the other day some fonts in my Publisher documents are now showing Exclamation mark (!) in front of the name and Font Manager says "Unsupported characters used".
I have read some topics here about the issue, I get an idea what the problem is but can't find solution. Just to mention that before upgrade I absolutely did NOT have that issue.

Now suddenly seems like a lots of my fonts on my computer that I used before are not working properly in Affinity. I would say about 30% of fonts are now showing with Exclamation mark?!?

Any idea why is this happening, are you guys aware of the issue, are you working on an update to rectify this.

The exclamation mark indicates, as the message indicated, that you've used a character that is not present in the font. When you do that, either you'll get a "not found" symbol (often an empty rectangle) or, more usually, the character will be substituted with one from another font you have installed that does contain that character.

Could you copy and paste one of the text boxes that shows the issue into a new document and attach it here? I can check it on MacOS 12 as well as 13 and see if the behaviour is different. But as @walt.farrellhas pointed out, normally when you see this, you need to use a font that does have that character or pick a different but supported character.

c80f0f1006