feat: translate all pages, UI messages and docs and fix SEO redirects and indexing

This commit is contained in:
alam00000 committed 2026-10-25 12:55:21 +05:30
1 parent 5e019de5ae
commit 4edb1718cc
3344 files changed
+415643 -4759

No files matched your search

+2 -2
View File
@@ -1,9 +1,9 @@
---
title: Encrypt PDF
title: Protect PDF
description: Password-protect PDF files with 256-bit AES encryption. Set user and owner passwords with configurable usage restrictions.
---
# Encrypt PDF
# Protect PDF
Lock your PDF behind a password so only authorized people can open it. BentoPDF uses 256-bit AES encryption -- the same standard used by banks and government agencies -- applied entirely in your browser via QPDF.
+2 -2
View File
@@ -1,9 +1,9 @@
---
title: Decrypt PDF
title: Unlock PDF
description: Remove password protection from encrypted PDFs. Supports batch decryption with a single password for multiple files.
---
# Decrypt PDF
# Unlock PDF
If you have the password to an encrypted PDF, this tool removes the encryption entirely, producing an unlocked copy that anyone can open without credentials. It supports batch decryption when multiple PDFs share the same password.
+2 -2
View File
@@ -30,7 +30,7 @@ The tool extracts PKCS#7 signature objects from the PDF, decodes the ASN.1 struc
- The tool reconstructs the bytes covered by the signature's `/ByteRange`, hashes them with the algorithm the signer declared, and compares the result against the `messageDigest` attribute inside the signature.
- It then re-serializes the signed attributes as a DER SET and verifies the signature against the signer certificate's public key.
- **A signature is reported as valid only when all of these pass.** If the PDF bytes were modified after signing, or the embedded signature does not match the signer's key, the status shows "Invalid — Cryptographic Verification Failed" with the specific reason.
- **A signature is reported as valid only when all of these pass.** If the PDF bytes were modified after signing, or the embedded signature does not match the signer's key, the status shows "Invalid: Cryptographic Verification Failed" with the specific reason.
#### Supported Signature Algorithms
@@ -40,7 +40,7 @@ The tool extracts PKCS#7 signature objects from the PDF, decodes the ASN.1 struc
| RSA-PSS (RSASSA-PSS) | Web Crypto `verify({name: 'RSA-PSS', saltLength})` |
| ECDSA P-256/P-384/P-521 | Web Crypto `verify({name: 'ECDSA', hash})` after DER → IEEE P1363 signature conversion |
If a signature uses an algorithm outside this list (for example Ed25519, SM2, or RSA with an unusual digest OID), the card shows **"Unverified — Unsupported Signature Algorithm"** in yellow, along with the specific OID or reason. This is a deliberate three-state distinction:
If a signature uses an algorithm outside this list (for example Ed25519, SM2, or RSA with an unusual digest OID), the card shows **"Unverified: Unsupported Signature Algorithm"** in yellow, along with the specific OID or reason. This is a deliberate three-state distinction:
- **Valid** — signature cryptographically verified against the signer's public key.
- **Invalid** — verification ran and produced a negative result (bytes changed, key mismatch).