acl-org / acl-org/acl-anthology
Ingestion Request: LaTeLL 2026
- Dominant language
- Python
- Stars
- 797
- Forks
- 408
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 36
Description
### General information about this request
- [x] I confirm that I have read the [Information for Submitters](https://aclanthology.org/info/contrib/).
- [x] I am submitting a request for a **new venue** that does not exist in the ACL Anthology yet.
### Venue Identifier
latell
### ACL SIG(s) sponsoring or endorsing the whole venue
_No response_
### Volume Title
Proceedings of the First International Conference on Language Technologies for Low-resource Languages (LaTeLL 2026)
### Venue Name (only if you are submitting a new venue)
International Conference on Language Technologies for Low-resource Languages
### Venue Website (only if you are submitting a new venue)
https://latell.org/2026/
### Date of Publication
28 September 2026
### Location
Fes, Morocco
### Submission Platform(s)
- [ ] OpenReview (proceedings compiled with [aclpub2](https://github.com/rycolab/aclpub2/))
- [x] Softconf/START (export the proceedings in ACLPUB format; no need to convert with aclpub2)
- [ ] Other (explain)
### ORCID iDs
- [x] We will instruct authors to supply ORCID information in their profiles in the submission platform ([instructions](https://aclanthology.org/info/author-pages/)). (Not necessary for historical volumes.)
### Delivery Method
- [x] Private Github repo (preferred)
- [ ] wget-able web link (HTTP, FTP)
- [ ] Proprietary file sharing service (Google Drive or Dropbox)
### Supporting Information
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or run steps are referenced in the issue body. Begin by checking prior approved ingestion requests in this repository to locate where venue records are stored, then add a `latell` venue entry using the provided identifier, title, date, location, website, and Softconf/START details. There is no automated test in the payload; done means LaTeLL 2026 is present in the same ingestion format/location as existing venues and ready for private GitHub delivery.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100