Max Font Size Constraints and Dedicated File Attachment Fields

[Fatih]

Hello,

After extensively working with the Form tools, I would like to propose two feature enhancements that would significantly improve the user experience and visual consistency of professional PDF forms.

1. Maximum Font Size Limit for "Auto" Text Fields
Currently, the "Auto" font size feature is excellent for ensuring long strings of text fit within a defined area. However, it presents a visual branding issue with shorter inputs: a single word or a name often scales up to a disproportionately large size, looking inconsistent with the rest of the document.

• Proposed Solution: Add a "Max Font Size" property to the Text Field Properties (Appearance tab).
  Behavior: If the text is short, it should stay at the defined maximum (e.g., 12pt). If the text exceeds the field boundaries, it should then begin to sca

le down automatically as it currently does.[/list]

2. Native "Attach File" Form Field
While Pro users can use the global attachment tools, many end-users rely on basic readers (like Adobe Reader) where the "Comment" attachment tool is often buried or restricted. Adding a dedicated Form Field for file attachments would provide a more intuitive workflow for data collection.

• Current Workaround: Using the "Add Attachment" icon in the Comments section of PDF X-Change, which lacks field-level context.
  Proposed Solution: A new "File Attachment" field type in the Form Builder.
  Benefit: This would allow form creators to place specific "Upload" buttons in relevant sections of a document (e.g., "Attach ID here" or "Attach Receipt here"), making the form much more structured and user-friendly for non-Pro users.

3. Integrated Data Validation for Common Form Inputs
While the "Special" formatting tab exists, it is currently limited and often lacks support for international formats. Users currently have to write custom JavaScript to ensure an email address is valid or that a URL follows the correct syntax.

• Proposed Solution: Add native Validation Presets within the Field Properties.
  Target Fields: * Email: Automatic check for @ and domain suffix.
  URL: Validation for http://, https://, www. or abc.com prefixes.
  Phone Numbers: Flexible masks that support international country codes.

Benefit: This lowers the barrier to entry for form creators who aren't familiar with JavaScript regex (Regular Expressions) and ensures higher data integrity for collected responses.

I believe these additions would offer much-needed flexibility for those of us designing complex, professional-grade forms. I look forward to hearing if these are on the roadmap or if there are any planned API improvements to support this via JavaScript.

Regards,

[Daniel - PDF-XChange]

Hello, Fatih

Thank you for the email and suggestions. I will tackle each of these by point.

1. Unfortunately, the available properties are defined by the PDF Specification. We cannot add a new one without risking damage to your file, and so this item will not be possible at this time.

2. The "button" field can already do this:

image.png

Beyond that I am once again sorry to say the the PDF Specification heavily restricts what solutions are available to us. It explicitly defines the available field types and their capabilities, applicable properties, the works. We have very little freedom in making additions to these functions.

3. Now this last option - this one may be possible. I believe that the Special formatting category is simply pre-written JS actions we offer in the software, which gives notably more freedom in implementation. I will pass along your suggested new modes for their consideration.

Kind regards,

[Fatih]

Hi Daniel,

I really appreciate your quick response. I was not aware how button function is powerful.

And thanks again your consideration for field validations.

[Daniel - PDF-XChange]