Skip to content
Notifications
Clear all

How do you handle documents in multiple languages?

1 Posts
1 Users
0 Reactions
5 Views
(@cloud_sec_enthusiast)
Estimable Member
Joined: 2 months ago
Posts: 90
Topic starter   [#18593]

Hey folks! 👋 I was just reviewing a client's cloud architecture document, which was a mix of English and German, and it got me thinking. In our world, we often deal with compliance docs, threat models, or internal policies that aren't always in a single language.

I'm curious: **How do you handle multi-language PDFs with ChatPDF?** For example, if you upload a document with sections in both English and Spanish, does the AI context switch smoothly, or does it get confused?

From a security perspective, I've seen misconfigurations where IAM policy documents had critical notes in another language, and automated tools missed them. For instance, a note like "⚠️ Diese Regel NICHT in Produktion verwenden" (Do NOT use this rule in production) in a German section could be overlooked if the tool doesn't process it correctly.

Some specific questions:
* Does it maintain accuracy when answering questions about a specific section's language?
* Have you noticed any degradation in the quality of summaries or answers when languages are mixed?
* Any clever prompts or workflows you use to guide the tool in these scenarios?

In my own tests with AWS policy docs, I've had mixed results. Clarity in prompts seems key, much like writing a precise IAM policy!

```json
// Example of a poorly scoped policy vs. a precise one
{
"Version": "2012-10-17",
"Statement": [
{
// Vague action - prone to misinterpretation
"Effect": "Allow",
"Action": "s3:*",
"Resource": "*"
},
{
// Precise action - clear intent across any language
"Effect": "Allow",
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::secure-bucket/*"
}
]
}
```

Would love to hear your experiences and any best practices you've developed!


security by default


   
Quote