REVIEW 3 cited by
Style Transformer: Unpaired Text Style Transfer without Disentangled Latent Representation
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
Disentangling the content and style in the latent space is prevalent in unpaired text style transfer. However, two major issues exist in most of the current neural models. 1) It is difficult to completely strip the style information from the semantics for a sentence. 2) The recurrent neural network (RNN) based encoder and decoder, mediated by the latent representation, cannot well deal with the issue of the long-term dependency, resulting in poor preservation of non-stylistic semantic content. In this paper, we propose the Style Transformer, which makes no assumption about the latent representation of source sentence and equips the power of attention mechanism in Transformer to achieve better style transfer and better content preservation.
Forward citations
Cited by 3 Pith papers
-
Embedding Style Beyond Topics: Analyzing Dispersion Effects Across Different Language Models
On a Queneau-Fénéon corpus, topic variation increases embedding dispersion more than style variation, but the style effect is confounded with human versus GPT-4o authorship.
-
StyleRWKV: High-Quality and High-Efficiency Style Transfer with RWKV-like Architecture
StyleRWKV applies recurrent RWKV-style attention with deformable shifting and skip scanning to achieve fast, high-quality arbitrary style transfer.
-
Mitigating Stylistic Biases of Machine Translation Systems via Monolingual Corpora Only
Babel detects and repairs stylistic mismatches in machine translation outputs using a style detector and a diffusion-based applicator trained on monolingual corpora.
Discussion (0). Continue with ORCID to comment.