$ afasi versionFuzz a language by mixing up only few words. version 2021.10.22
General Help
$ afasiUsage: afasi [OPTIONS] COMMAND [ARGS]... Fuzz a language by mixing up only few words. The translation table entries are applied in order per line of input. So, with large translation tables the performance will obviously degrade with a power of two. The latter should be taken as a hint to maintain both language files in separate entities not as a patch task. The translation table is either an array of two element arrays provided as JSON and thus shall be in a shape like: [ ["repl", "ace"], ["als", "othis"] ] Or the table is given as an object providing more detailed instructions constraining the translation rules like: * contra indicators - when given exempting a line from translation * pro indicators - when given marking a line for translation * flip_flop indicators - providing either stop-start (default) or start-stop state switching The JSON object format is best understood when executing the template command and adapting the resulting JSON object written to standard out. Default for input source is standard in and out per default is sent to standard out.Options: -V, --version Display the afasi version and exit -h, --help Show this message and exit.Commands: template Write a template of a translation table JSON structure to... translate Translate from a language to a 'langauge'. version Display the afasi version and exit
Translate Help
$ afasi translate -hUsage: afasi translate [OPTIONS] [SOURCE] [TARGET] Translate from a language to a 'langauge'.Arguments: [SOURCE] [default: STDIN] [TARGET] [default: STDOUT]Options: -i, --input
Path to input file (default is reading from
standard in) -o, --output
Path to non-existing output file (default is
writing to standard out) -t, --table
Path to translation table file in JSON format. Structure of table data is [["repl", "ace"], ["als", "othis"]] -n, --dryrun Flag to execute without writing the translation but a diff instead (default is False) -h, --help Show this message and exit.
Translate Dryrun
Rock' -> '>Lounge' 2. '>Track' -> '>Rock' * diff of source to target: --- SOURCE +++ TARGET @@ -6,12 +6,12 @@ Some Track
Does not matter.
-
Track
+
Rock
Some Rock
Does not matter.
-
Rock
+
Lounge
# --- ">
$ afasi translate minimal-in.xml --table minimal.json --dryrundryrun requested
# ---* resources used: - input from: "minimal-in.xml" - output to: STDOUT - translation from: "minimal.json"* translations (in order): 1. '>Rock' -> '>Lounge' 2. '>Track' -> '>Rock'* diff of source to target:--- SOURCE+++ TARGET@@ -6,12 +6,12 @@Some Track
Does not matter.
-
Track
+
Rock
Some Rock
Does not matter.
-
Rock
+
Lounge
# ---
Translate
Some Track
Does not matter.
-
Track
+
Rock
Some Rock
Does not matter.
-
Rock
+
Lounge
">
$ afasi translate --input minimal-in.xml --output minimal-out.xml --table minimal.json
$ afasi % diff -u minimal-*.xml--- minimal-in.xml 2021-10-20 20:12:54.000000000 +0200+++ minimal-out.xml 2021-10-20 20:14:45.000000000 +0200@@ -6,12 +6,12 @@Some Track
Does not matter.
-
Track
+
Rock
Some Rock
Does not matter.
-
Rock
+
Lounge
The translation table entries are applied in order per line of input. So, with large translation tables the performance will obviously degrade with a power of two. The latter should be taken as a hint to maintain both language files in separate entities not as a patch task.
The translation table is either an array of two element arrays provided as JSON and thus shall be in a shape like:
[
["repl", "ace"],
["als", "othis"]
]
Or the table is given as an object providing more detailed instructions constraining the translation rules like:
contra indicators - when given exempting a line from translation
pro indicators - when given marking a line for translation
flip_flop indicators - providing either stop-start (default) or start-stop state switching
The JSON object format is best understood when executing the template command and adapting the resulting JSON object written to standard out.
Default for input source is standard in and out per default is sent to standard out.
Usage:
$ afasi [OPTIONS] COMMAND [ARGS]...
Options:
-V, --version: Display the afasi version and exit [default: False]
-h, --help: Show this message and exit.
Commands:
template: Write a template of a translation table JSON...
translate: Translate from a language to a 'langauge'.
version: Display the afasi version and exit
afasi template
Write a template of a translation table JSON structure to standard out and exit
Usage:
$ afasi template [OPTIONS]
Options:
-h, --help: Show this message and exit.
afasi translate
Translate from a language to a 'langauge'.
Usage:
$ afasi translate [OPTIONS] [SOURCE] [TARGET]
Arguments:
[SOURCE]: [default: STDIN]
[TARGET]: [default: STDOUT]
Options:
-i, --input
: Path to input file (default is reading from standard in) [default: ]
-o, --output
: Path to non-existing output file (default is writing to standard out) [default: ]
-t, --table
: Path to translation table file in JSON format. Structure of table data is [["repl", "ace"], ["als", "othis"]] [default: ]
-n, --dryrun: Flag to execute without writing the translation but a diff instead (default is False) [default: False]
Automates much of the process of moving translations from the old Multilingual external module to the newer built-in Multi-Language Management (MLM) page.
A wordlist generator tool, that allows you to supply a set of words, giving you the possibility to craft multiple variations from the given words, creating a unique and ideal wordlist to use regarding a specific target.
SnapMix: Semantically Proportional Mixing for Augmenting Fine-grained Data (AAAI 2021) PyTorch implementation of SnapMix | paper Method Overview Cite
Releases(v2021.10.28)
v2021.10.28(Dec 28, 2021)
afasi
Fuzz a language by mixing up only few words.
v2021.10.28
Happy linter, happy winter
Installation
Preferred way to install is as usual (for testing or in isolation):
$ pipx install afasi
For production use (well, ahem, ...) or within a virtual python env:
$ pip install afasi
Use
Examples
Version
$ afasi version
Fuzz a language by mixing up only few words. version 2021.10.28
General Help
$ afasi
Usage: afasi [OPTIONS] COMMAND [ARGS]...
Fuzz a language by mixing up only few words.
The translation table entries are applied in order per line of input. So,
with large translation tables the performance will obviously degrade with a
power of two. The latter should be taken as a hint to maintain both language
files in separate entities not as a patch task.
The translation table is either an array of two element arrays provided as
JSON and thus shall be in a shape like:
[
["repl", "ace"],
["als", "othis"]
]
Or the table is given as an object providing more detailed instructions
constraining the translation rules like:
* contra indicators - when given exempting a line from translation
* pro indicators - when given marking a line for translation
* flip_flop indicators - providing either stop-start (default) or start-stop state switching
The JSON object format is best understood when executing the template
command and adapting the resulting JSON object written to standard out.
Default for input source is standard in and out per default is sent to
standard out.
Options:
-V, --version Display the afasi version and exit
-h, --help Show this message and exit.
Commands:
template Write a template of a translation table JSON structure to...
translate Translate from a language to a 'langauge'.
version Display the afasi version and exit
Translate Help
$ afasi translate -h
Usage: afasi translate [OPTIONS] [SOURCE] [TARGET]
Translate from a language to a 'langauge'.
Arguments:
[SOURCE] [default: STDIN]
[TARGET] [default: STDOUT]
Options:
-i, --input <sourcepath> Path to input file (default is reading from
standard in)
-o, --output <targetpath> Path to non-existing output file (default is
writing to standard out)
-t, --table <translation table path>
Path to translation table file in JSON
format. Structure of table data is [["repl",
"ace"], ["als", "othis"]]
-n, --dryrun Flag to execute without writing the
translation but a diff instead (default is
False)
-h, --help Show this message and exit.
The translation table entries are applied in order per line of input.
So, with large translation tables the performance will obviously degrade with a power of two.
The latter should be taken as a hint to maintain both language files in separate entities not as a patch task.
The translation table is either
an array or two element arrays provided as JSON and thus shall be in a shape like:
[
["repl", "ace"],
["als", "othis"]
]
or an object allowing for pro, contra replace indications, flip-flop behavior and more (see help for more info).
Default for input source is standard in and out per default is sent to standard out.
The translation table entries are applied in order per line of input.
So, with large translation tables the performance will obviously degrade with a power of two.
The latter should be taken as a hint to maintain both language files in separate entities not as a patch task.
The translation table is an array or two element arrays provided as JSON and thus shall be in a shape like:
[
["repl", "ace"],
["als", "othis"]
]
Default for input source is standard in and out per default is sent to standard out.
The translation table entries are applied in order per line of input.
So, with large translation tables the performance will obviously degrade with a power of two.
The latter should be taken as a hint to maintain both language files in separate entities not as a patch task.
The translation table is an array or two element arrays provided as JSON and thus shall be in a shape like:
[
["repl", "ace"],
["als", "othis"]
]
Default for input source is standard in and out per default is sent to standard out.
Working with teams, changing things and the way we work.
Any personal contribution of this user is MIT licensed.
Opinions expressed on behalf of himself only.
Microsoft's Cascadia Code font customized to my liking. Also includes some simple batch patch and bake scripts to batch patch glyphs and bake font features into fonts!
This is an AI that is supposed to say you if your text is formal or not. It's written in Python 3 and has some german examples (because I'm german yk) in the text.json file. This file contains the te
3 Oct 9, 2021
3 Sep 27, 2022
319 Dec 30, 2022
1 Jan 1, 2022
6 Nov 20, 2022
39 Dec 10, 2022
1 Oct 19, 2021
14 Sep 30, 2022
14 Mar 25, 2022
3 Oct 14, 2022
221 Jan 1, 2023
67 Oct 25, 2022
3 Dec 22, 2021
46 Nov 30, 2022
218 Jan 5, 2023
393 Dec 13, 2022
32 Oct 14, 2022
126 Dec 30, 2022
4 Jan 22, 2022
1.2k Dec 16, 2022
1 Oct 20, 2021
111 Dec 19, 2022
4 Dec 05, 2022
29 Dec 20, 2022
3 Jan 29, 2022
1.7k Dec 27, 2022
4 Nov 28, 2021
1 Nov 09, 2021
13 Nov 05, 2021
3 Jun 14, 2022
1 Jan 12, 2022
0 Sep 25, 2022
1 Jan 06, 2022
1.8k Dec 31, 2022
98 Jan 07, 2023
2 Jun 30, 2022
18 Dec 19, 2022
2 Nov 03, 2022