Antoine Clausse
0e4fe4090a
* Add tests on plurals * Update `collabs_per_proj` and its pluralisations * Update `n_user` and its pluralisations * Update `showing_x_results` and its pluralisations * Update `show_x_more_projects` and its pluralisations * `bin/run web npm run extract-translations` * Populate `_plural` keys in non-en locales For 2-form languages (da, de, es, fi, fr, it, nl, no, pt, sv, tr), copy the existing bare-key value into the new `_plural` sibling to prevent i18next from falling back to English for count!=1. Also remove orphan singular keys (`collabs_per_proj_single`, `showing_1_result*`) left over from the previous commits. Bare-key values remain in their original plural form pending translator review — count=1 will still render the plural form in non-en until translators flip those to singular. Multi-form (cs, pl, ru) and single-form (ja, ko, zh-CN, zh-TW) locales are unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Flip non-en bare-key values to singular form Per review, the i18next v3 plural convention uses the bare key for count=1 (singular) and `_plural` for count!=1. The non-en bare-key values were left as the original plural form by the previous commit so the `_plural` siblings could be copied from them; this commit flips the bare values to the singular form per language. Languages where singular and plural noun forms coincide (Finnish, Swedish, Turkish) are unchanged. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> * Apply suggestions from code review Co-authored-by: Olzhas Askar <olzhas.askar@gmail.com> --------- Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com> Co-authored-by: Olzhas Askar <olzhas.askar@gmail.com> GitOrigin-RevId: 628513ca792c2dcce023247e52b7320e2741cc54
An open-source online real-time collaborative LaTeX editor.
Wiki • Server Pro • Contributing • Mailing List • Authors • License
Figure 1: A screenshot of a project being edited in Overleaf Community Edition.
Community Edition
Overleaf is an open-source online real-time collaborative LaTeX editor. We run a hosted version at www.overleaf.com, but you can also run your own local version, and contribute to the development of Overleaf.
Caution
Overleaf Community Edition is intended for use in environments where all users are trusted. Community Edition is not appropriate for scenarios where isolation of users is required due to Sandbox Compiles not being available. When not using Sandboxed Compiles, users have full read and write access to the
sharelatexcontainer resources (filesystem, network, environment variables) when running LaTeX compiles.
For more information on Sandbox Compiles check out our documentation.
Enterprise
If you want help installing and maintaining Overleaf in your lab or workplace, we offer an officially supported version called Overleaf Server Pro. It also includes more features for security (SSO with LDAP or SAML), administration and collaboration (e.g. tracked changes). Find out more!
Keeping up to date
Sign up to the mailing list to get updates on Overleaf releases and development.
Installation
We have detailed installation instructions in the Overleaf Toolkit.
Upgrading
If you are upgrading from a previous version of Overleaf, please see the Release Notes section on the Wiki for all of the versions between your current version and the version you are upgrading to.
Overleaf Docker Image
This repo contains two dockerfiles, Dockerfile-base, which builds the
sharelatex/sharelatex-base image, and Dockerfile which builds the
sharelatex/sharelatex (or "community") image.
The Base image generally contains the basic dependencies like wget, plus texlive.
We split this out because it's a pretty heavy set of
dependencies, and it's nice to not have to rebuild all of that every time.
The sharelatex/sharelatex image extends the base image and adds the actual Overleaf code
and services.
Use make build-base and make build-community from server-ce/ to build these images.
We use the Phusion base-image
(which is extended by our base image) to provide us with a VM-like container
in which to run the Overleaf services. Baseimage uses the runit service
manager to manage services, and we add our init-scripts from the server-ce/runit
folder.
Contributing
Please see the CONTRIBUTING file for information on contributing to the development of Overleaf.
Authors
License
The code in this repository is released under the GNU AFFERO GENERAL PUBLIC LICENSE, version 3. A copy can be found in the LICENSE file.
Copyright (c) Overleaf, 2014-2025.