Browse State-of-the-Art › Formality Style Transfer
Formality Style Transfer
10 papers with code · 1 benchmark · 1 dataset archive 2025-07-28
Formality Style Transfer
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
1 leaderboard table shown for this task, 1 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.
Syntology 1 newer paper was judged to report on this task's benchmarks so far (Claude Sonnet 4.5, reading their tables: a model's judgement, not a result; 0 placed): GYAFC (1 judged, 0 placed). Drawn from 8,886 of 18,637 newer papers checked so far (733 more had nothing to place; 41 could not be read).
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| GYAFC (1 row) | Consistency Training | Semi-Supervised Formality Style Transfer with Consistency Training | code | Syntology official (archive's flag): 1 ran · 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result | Compare |
Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Libraries
Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.
Datasets archive 2025-07-28
1 dataset whose archive record lists this task, ordered by the archive's paper count.
Subtasks archive 2025-07-28
No subtask under this task in the archive's task tree.
Parent tasks archive 2025-07-28
Papers archive 2025-07-28
archive papers tagged: 19 · with a code link: 10 · where Syntology ran a sample: 2 (2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology
Show: all tagged papersonly where code ran (2 of 19 tagged: 2 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument)
Page 1 of 1: papers 1 to 19 of 19, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.
Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.
-
20 Oct 2021 2 repositories listedWhile the field of style transfer (ST) has been growing rapidly, it has been hampered by a lack of standardized practices for automatic evaluation.
-
15 Sep 2023 1 repository listedVia automatic and human evaluation, we show that specialized student models fine-tuned on our datasets outperform generalist teacher models on the explainable style transfer task in one-shot settings, and perform…
-
17 May 2023 1 repository listedWe present a large language model fine-tuned on a diverse collection of task-specific instructions for text editing (a total of 82K instructions).
-
25 Mar 2022 1 repository listed Syntology official (archive's flag): 1 ran · 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result (of 1 harvested sample)In this work, we propose a simple yet effective semi-supervised framework to better utilize source-side unlabeled sentences based on consistency training.
-
14 May 2021 1 repository listedScarcity of parallel data causes formality style transfer models to have scarce success in preserving content.
-
8 Apr 2021 1 repository listed Syntology official: no sample here; runs from other or unrecorded repositories · 1 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 2 unverified (of 3 harvested samples)We take the first step towards multilingual style transfer by creating and releasing XFORMAL, a benchmark of multiple formal reformulations of informal text in Brazilian Portuguese, French, and Italian.
-
1 Dec 2020 1 repository listedConventional approaches for formality style transfer borrow models from neural machine translation, which typically requires massive parallel data for training.
-
10 Oct 2020 1 repository listedFormality style transfer is the task of converting informal sentences to grammatically-correct formal sentences, which can be used to improve performance of many downstream NLP tasks.
-
14 May 2020 1 repository listedThe main barrier to progress in the task of Formality Style Transfer is the inadequacy of training data.
-
17 Mar 2018 1 repository listedStyle transfer is the task of automatically transforming a piece of text in one particular style into another.
-
Formality Style Transfer in Persian2 Jun 2024 0 repositories listedThis study explores the formality style transfer in Persian, particularly relevant in the face of the increasing prevalence of informal language on digital platforms, which poses challenges for existing Natural Language…
-
Reducing Sequence Length by Predicting Edit Operations with Large Language Models19 May 2023 0 repositories listedLarge Language Models (LLMs) have demonstrated remarkable performance in various tasks and gained significant attention.
-
Improving Formality Style Transfer with Context-Aware Rule Injection1 Jun 2021 0 repositories listedModels pre-trained on large-scale regular text corpora often do not work well for user-generated data where the language styles differ significantly from the mainstream text.
-
Olá, Bonjour, Salve! XFORMAL: A Benchmark for Multilingual Formality Style Transfer1 Jun 2021 0 repositories listedWe take the first step towards multilingual style transfer by creating and releasing XFORMAL, a benchmark of multiple formal reformulations of informal text in Brazilian Portuguese, French, and Italian.
-
Formality Style Transfer for Noisy, User-generated Conversations: Extracting Labeled, Parallel Data from Unlabeled Corpora1 Nov 2019 0 repositories listedTypical datasets used for style transfer in NLP contain aligned pairs of two opposite extremes of a style.
-
Harnessing Pre-Trained Neural Networks with Rules for Formality Style Transfer1 Nov 2019 0 repositories listedFormality text style transfer plays an important role in various NLP applications, such as non-native speaker assistants and child education.
-
Sequence-to-sequence Pre-training with Data Augmentation for Sentence Rewriting13 Sep 2019 0 repositories listedWe study sequence-to-sequence (seq2seq) pre-training with data augmentation for sentence rewriting.
-
Automatic Grammatical Error Correction for Sequence-to-sequence Text Generation: An Empirical Study1 Jul 2019 0 repositories listedSequence-to-sequence (seq2seq) models have achieved tremendous success in text generation tasks.
-
Formality Style Transfer with Hybrid Textual Annotations15 Mar 2019 0 repositories listedFormality style transformation is the task of modifying the formality of a given sentence without changing its content.
Syntology lines on 2 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections