(You can find a runnable example here: FillFormCustomFont.java)
Using poor-man's-bold
- How do I bold the field? ... What I need to set to bold the field?
In PDF you usually make text bold by using a font with bold glyphs, also see your second question. If you don't have such a bold font at hands, you may instead use some poor-man's-bold technique, e.g. not only filling the letter but also stroking a line along its borders:
public static void setFieldBold(String name, String value) throws IOException
{
PDDocumentCatalog docCatalog = _pdfDocument.getDocumentCatalog();
PDAcroForm acroForm = docCatalog.getAcroForm();
PDField field = acroForm.getField(name);
COSDictionary dict = ((PDField) field).getDictionary();
COSString defaultAppearance = (COSString) dict
.getDictionaryObject(COSName.DA);
if (defaultAppearance != null)
{
dict.setString(COSName.DA, "/Helv 10 Tf 2 Tr .5 w 0 g");
if (name.equalsIgnoreCase("Field1")) {
dict.setString(COSName.DA, "/Helv 12 Tf 0 g");
}
}
if (field instanceof PDTextbox)
{
field = new PDTextbox(acroForm, dict);
((PDField) field).setValue(value);
}
}
(2 Tr .5 w
= use rendering mode 2, i.e. fill and stroke, and use a line width of .5)
Instead of
you now get
Using custom fonts
- If I understand right, there are 14 basic fonts that I can use in PDFBox out of the box (pun unintended). I would like to use one or more fonts that look like Signatures (cursive). Any out of the box fonts that do that? If not, if I have my own font, how do I set in the method to be written to the PDF?
If you want to use an own font, you first need to register it in the AcroForm default resources like this:
public String prepareFont(PDDocument _pdfDocument) throws IOException
{
PDDocumentCatalog docCatalog = _pdfDocument.getDocumentCatalog();
PDAcroForm acroForm = docCatalog.getAcroForm();
PDResources res = acroForm.getDefaultResources();
if (res == null)
res = new PDResources();
InputStream fontStream = getClass().getResourceAsStream("LiberationSans-Regular.ttf");
PDTrueTypeFont font = PDTrueTypeFont.loadTTF(_pdfDocument, fontStream);
String fontName = res.addFont(font);
acroForm.setDefaultResources(res);
return fontName;
}
This method returns the font name to use in
public static void setField(String name, String value, String fontName) throws IOException
{
PDDocumentCatalog docCatalog = _pdfDocument.getDocumentCatalog();
PDAcroForm acroForm = docCatalog.getAcroForm();
PDField field = acroForm.getField(name);
COSDictionary dict = ((PDField) field).getDictionary();
COSString defaultAppearance = (COSString) dict
.getDictionaryObject(COSName.DA);
if (defaultAppearance != null)
{
dict.setString(COSName.DA, "/" + fontName + " 10 Tf 0 g");
if (name.equalsIgnoreCase("Field1")) {
dict.setString(COSName.DA, "/" + fontName + " 12 Tf 0 g");
}
}
if (field instanceof PDTextbox)
{
field = new PDTextbox(acroForm, dict);
((PDField) field).setValue(value);
}
}
You now get
The difference is not too big because the fonts are quite similar. Use the font of your choice for more effect.
Using /Helv, /HeBo, ...
The OP found a list of font names /Helv, /HeBo, ..., probably in the PDFBox issue PDFBOX-1234, which appear to be usable without defining them in any resource dictionary.
These names are not a PDF feature, i.e. the PDF specification does not know about them, on the contrary:
The default appearance string (DA) contains any graphics state or text state operators needed to establish the graphics state parameters, such as text size and colour, for displaying the field’s variable text. Only operators that are allowed within text objects shall occur in this string (see Figure 9). At a minimum, the string shall include a Tf (text font) operator along with its two operands, font and size. The specified font value shall match a resource name in the Font entry of the default resource dictionary (referenced from the DR entry of the interactive form dictionary; see Table 218).
(section 12.7.3.3 Field Dictionaries / Variable Text in ISO 32000-1)
Thus, the specification does not know those default font names.
Nonetheless, Adobe Reader/Acrobat seem to support them, most likely because at some time in the distant past some form generating tool assumed them to be there and support for those forms was kept due to compatibility reasons.
Using this feature, therefore, might not be the best choice but your mileage may vary.
Using custom and standard fonts
In his comments the OP indicated he wanted to use both custom and standard fonts in forms.
To do this I generalized the method prepareFont
a bit and refactored the TTF import into a separate method:
public List<String> prepareFont(PDDocument _pdfDocument, List<PDFont> fonts) throws IOException
{
PDDocumentCatalog docCatalog = _pdfDocument.getDocumentCatalog();
PDAcroForm acroForm = docCatalog.getAcroForm();
PDResources res = acroForm.getDefaultResources();
if (res == null)
res = new PDResources();
List<String> fontNames = new ArrayList<String>();
for (PDFont font: fonts)
{
fontNames.add(res.addFont(font));
}
acroForm.setDefaultResources(res);
return fontNames;
}
public PDFont loadTrueTypeFont(PDDocument _pdfDocument, String resourceName) throws IOException
{
try ( InputStream fontStream = getClass().getResourceAsStream(resourceName); )
{
return PDTrueTypeFont.loadTTF(_pdfDocument, fontStream);
}
}
Using these methods you can mix custom and standard fonts like this:
PDDocument doc = PDDocument.load(originalStream);
List<String> fontNames = prepareFont(doc, Arrays.asList(loadTrueTypeFont(doc, "LiberationSans-Regular.ttf"), PDType1Font.HELVETICA_BOLD));
setField(doc, "FirstName", "My first name", fontNames.get(0));
setField(doc, "LastName", "My last name", fontNames.get(1));
doc.save(new File(RESULT_FOLDER, "acroform-setFieldCustomStandard.pdf"));
doc.close();
(FillFormCustomFont.testSetFieldCustomStandard_acroform)
Resulting in
PDType1Font
has constants for all 14 standard fonts. Thus, like this you can use standard fonts (mixed with custom fonts if desired) in form fields in a way that generates the proper Font entries in the default resources, i.e. without relying on proprietary default font names like HeBo.
PS
Any documentation on what order the /Helv 10 Tf 0 g are arranged?
Yes, there is, cf. the specification ISO 32000-1.