Here is the text we could read:
COMMONWEALTH OF PENNSYLVANIA
COUNTY OF ____________
ORDER DENYING PETITION FOR
EMERGENCY RELIEF IN CONNECTION WITH
CLAIMS OF SEXUAL VIOLENCE
OR INTIMIDATION
ដ
ី ប ប់បដិេសធមិនឲ នបណឹងស ប់ជំនួយសេ
ះប ន់
ប់ ក់ព័ន មួ យនឹង រ ម រ
ៃនអំេពហិង ឬ
រគំ មកំ ែហងផ វេភទ
Mag. Dist. No:
េលខស ល់េ កមស ត់
MDJ Name:
េ
ះេ កមស ត់
Address:
សយ ន
Telephone:
េលខទូរស័ព
_________________________
vs.
_________________________
Docket No / េលខប ីបណឹង៖
Case Filed / សំណុ
ំេរ ង៖
ORDER
DENYING PETITION FOR EMERGENCY RELIEF IN
CONNECTION WITH CLAIMS OF SEXUAL VIOLENCE OR
INTIMIDATION
ដ
ី ប ប់
បដិេសធមិនឲ នបណឹងស ប់ជំនួយសេ
ះប ន់ ប់ ក់ទង
ម
ួ យនឹង រ ម រ
ៃនអំេពហិង ឬ
រគំ មកំ ែហងផ វេភទ
At an ex parte hearing held on _______________________, I
have found that it is not necessary to issue a protective order
and the petition for emergency relief is denied.
េ យ ប់ ក់ទងេ នឹង វ
ៃថទី_________________________________ខំ នរកេឃញ
ំ ច់េដម ីេចញនូ វដី
មិន ន រ
រមួ យ ែដលេធេឡងេ
ះេទ
រេ
រ
េហយបណឹង ស ប់ជំនួ យសេ
ះប ន់ តវ នបដិេសធេ ល។
_________________________ __________________________________________
Date / លបរ េចទ
Magisterial District Judge / េ កមស ត់
MDJS 306E-BL (Khmer / Cambodian)
1
Date Created: December 26, 2016
Khmer Order Denying Petition for Emergency Relief in Connection with Claims of Sexual Violence or Intimidation 306E
This info page is part of the LIT Lab's Form Explorer project. It is not associated with the Pennsylvania state courts.
To learn more about the project, check out our about page.
Downloads: You can download both the original form (last checked 2023-03)
and the machine-processed form with normalized data fields.
About This Form:
- Sourced from www.pacourts.us (2023-03)
- Page(s): 1
- Fields(s): 14
- Average fields per page: 14
- Reading Level: Grade 5
- LIST Grouping(s):
GO-00-00-00-00.
Use our Rate My PDF tool to learn more.
Go beyond the above insights and learn more about this or any pdf form at
RateMyPDF.com, includes: counts of difficult words used,
passive voice decetion, and suggestions for how to make the form more usable.
Identified Data Fields:
We have done our best to automaticly identify and name form fields according to our naming conventions.
When possible, we've used names tied to our question library. See e.g., user1_name.
If we think we've found a match to a question in our library, it is highlighted in green. Novel names are auto generated. So, you will probably need to edit some of them if you're trying to stick to the convention.
Here are the fields we could identify.
count
was COUNTY OF (0.54 conf)vs
was vs (0.33 conf)undefined
was undefined (0.38 conf)found_necessary_order
was have found that it is not necessary to issue a protective order (0.37 conf)fill__1
was fill_12 (0.36 conf)fill__2
was fill_11 (0.36 conf)š
was š (0.39 conf)ëáš_á
was ËÁŠ Á (0.38 conf)œš
was œŠ (0.35 conf)signature_date
was Date (1.00 conf)š_á
was š Á (0.34 conf)magisterial_district_judge
was Magisterial District Judge Á (0.41 conf)ÿ
was Ÿ (0.35 conf)ë
was Ë (0.35 conf)
We've done our best to group similar variables togther to avoid overwhelming the user.
Suggested Screen 0:
count
vs
undefined
found_necessary_order
fill__1
fill__2
ëáš_á
œš
signature_date
magisterial_district_judge
ÿ
Suggested Screen 1:
Suggested Screen 2:
Create an Interactive Version of this Form:
The Weaver creates a draft guided interview from a template form, like the one provided here. You can use the link below to open this form in the Weaver.
To learn more, read "Weaving" your form into a draft interview.
Launch Form in Weaver