summaryrefslogtreecommitdiff
path: root/support/arara/source/src/main/resources
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-09-17 03:00:50 +0000
committerNorbert Preining <norbert@preining.info>2019-09-17 03:00:50 +0000
commitcda3ce3f9172e48d4bc673e57fc617ba0f0b40d1 (patch)
tree338fb039e5af66237ec0e6557f32b0784f022b61 /support/arara/source/src/main/resources
parent111dc5512e3db14318e26b6700731c68c41c1724 (diff)
CTAN sync 201909170300
Diffstat (limited to 'support/arara/source/src/main/resources')
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages.properties3
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_de.properties3
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en.properties3
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en_QN.properties3
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_it.properties3
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_nl.properties3
-rw-r--r--support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_pt_BR.properties3
7 files changed, 21 insertions, 0 deletions
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages.properties
index cdea39f1be..dd1972fd5c 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages.properties
@@ -63,6 +63,7 @@ ERROR_INTERPRETER_NULL_COMMAND=I am sorry, but apparently one of the provided co
ERROR_INTERPRETER_RULE_NOT_FOUND=I could not find a rule named ''{0}'' in the provided rule paths. Perhaps a misspelled word? I was looking for a file named ''{0}.yaml'' in the following paths in order of priority: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=I found these unknown keys in the directive: {0}. This should be an easy fix, just remove them from your map.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=The 'exit' expression must always return a boolean value (even if there is no computation in the closure body). This should be an easy fix: make sure to correct the type return statement and try again.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=The ''isSubdirectory'' method requires a directory, not a file. It looks like ''{0}'' does not appear to be a directory at all.
ERROR_LANGUAGE_INVALID_CODE=The provided language code is invalid. Currently, I know how to speak the following languages: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=I could not load the XML database named ''{0}''. I have no idea why it failed, though. Perhaps the file was moved or deleted before or during the reading operation. Or maybe I do not have the proper permissions to read the file. By the way, make sure the XML file is well-formed.
ERROR_PARSER_INVALID_PREAMBLE=I am sorry, but the preamble ''{0}'' could not be found. Please make sure this key exists in the configuration file.
@@ -110,6 +111,7 @@ ERROR_VELOCITY_IO_EXCEPTION=The template engine was not able to write the output
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=There are more details available on this exception:
INFO_DISPLAY_EXECUTION_TIME=Total: {0} seconds
INFO_DISPLAY_FILE_INFORMATION=Processing ''{0}'' (size: {1}, last modified: {2}), please wait.
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Although executing in dry-run mode, this entry might be already processed since it returned a boolean value: {0}
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=About to run: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Although executing in dry-run mode, this entry is always processed since it is a trigger. Note that the effects of a trigger might influence the current execution.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=This entry is a trigger originated from the rule scope. Note that the effects of a trigger might influence the current execution.
@@ -136,6 +138,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=set the execution timeout (in milliseconds)
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=print the command output
INFO_PARSER_VERSION_DESCRIPTION=print the application version
LOG_INFO_BEGIN_BUFFER=BEGIN OUTPUT BUFFER
+LOG_INFO_BOOLEAN_MODE=Boolean value: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIRECTIVES
LOG_INFO_END_BUFFER=END OUTPUT BUFFER
LOG_INFO_INTERPRET_RULE=I am ready to interpret rule ''{0}''.
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_de.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_de.properties
index 352259daf6..eb8bb41fd6 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_de.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_de.properties
@@ -63,6 +63,7 @@ ERROR_INTERPRETER_NULL_COMMAND=Es tut mir leid, aber eine der genutzten Anweisun
ERROR_INTERPRETER_RULE_NOT_FOUND=Ich konnte keine Regel mit dem Namen ''{0}'' in den hinterlegten Regelverzeichnissen finden. Vielleicht ein falsch geschriebenes Wort? Ich habe nach dem Dateinamen ''{0}.yaml'' in den nachstehenden Verzeichnissen mit entsprechender Priorität gesucht: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=Ich habe folgende unbekannte Keys in der Direktive gefunden: {0}. Das sollte leicht zu beheben sein, entferne sie einfach.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=Der Ausdruck 'exit' muss immer einen logischen Wert (boolean value) zurückgeben (sogar wenn es keine Berechnung in der Prozedur gibt). Das sollte leicht zu beheben sein: Stelle einen korrekten Rückgabewert sicher und versuche es erneut.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=Die ''isSubdirectory'' Methode erwartet als Argument einen Ordner, nicht eine Datei. ''{0}'' scheint kein Ordner zu sein.
ERROR_LANGUAGE_INVALID_CODE=Der bereitgestellte Sprachauswahlcode ist ungültig. Derzeit kann ich folgende Sprachen sprechen: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=Ich konnte die XML-Datenbank mit dem Namen ''{0}'' nicht laden. Ich habe keine Idee für die Fehlerursache, obwohl? Vielleicht wurde die Datei bevor oder während der Leseoperation bewegt oder gelöscht. Möglicherweise habe ich nicht die geeigneten Rechte, um die Datei zu lesen.
ERROR_PARSER_INVALID_PREAMBLE=Leider konnte die Präambel ''{0}'' nicht gefunden werden. Bitte stelle sicher, dass dieser Schlüssel in der Konfigurationsdatei existiert.
@@ -110,6 +111,7 @@ ERROR_VELOCITY_IO_EXCEPTION=Die Template-Engine konnte die Ausgabe-Datei nicht s
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=Es sind mehr Details für diese Ausnahme verfügbar.
INFO_DISPLAY_EXECUTION_TIME=Gesamt: {0} Sekunden
INFO_DISPLAY_FILE_INFORMATION=Verarbeitung ''{0}'' (Größe: {1}, letzte Modifikation: {2}), bitte warten.
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Trotz dry-run Modus wurde dieser Eintrag wahrscheinlich bereits verarbeitet, da er den boolschen Wert {0} zurückgegeben hat.
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=Los geht''s: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Obwohl du im 'dry-run-mode' ausführst, wird der Eintrag immer verarbeitet, da es einen Trigger ist. Beachte, dass der Effekt eines Triggers die aktuelle Ausführung beeinflussen kann.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=Dieser Eintrag ist ein Trigger, welcher aus dem Regelumfeld entstand. Beachte, dass der Effekt eines Triggers die aktuelle Ausführung beeinflussen kann.
@@ -136,6 +138,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=Setze die Zeitabschaltung für die Ausführung (
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=Gibt zusätzliche Statusinformationen aus
INFO_PARSER_VERSION_DESCRIPTION=Gebe die Anwendungsversion aus
LOG_INFO_BEGIN_BUFFER=BEGIN OUTPUT BUFFER
+LOG_INFO_BOOLEAN_MODE=Boolscher Wert: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIREKTIVEN
LOG_INFO_END_BUFFER=END OUTPUT BUFFER
LOG_INFO_INTERPRET_RULE=Ich bin bereit, die Regel ''{0}'' zu interpretieren.
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en.properties
index cdea39f1be..dd1972fd5c 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en.properties
@@ -63,6 +63,7 @@ ERROR_INTERPRETER_NULL_COMMAND=I am sorry, but apparently one of the provided co
ERROR_INTERPRETER_RULE_NOT_FOUND=I could not find a rule named ''{0}'' in the provided rule paths. Perhaps a misspelled word? I was looking for a file named ''{0}.yaml'' in the following paths in order of priority: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=I found these unknown keys in the directive: {0}. This should be an easy fix, just remove them from your map.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=The 'exit' expression must always return a boolean value (even if there is no computation in the closure body). This should be an easy fix: make sure to correct the type return statement and try again.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=The ''isSubdirectory'' method requires a directory, not a file. It looks like ''{0}'' does not appear to be a directory at all.
ERROR_LANGUAGE_INVALID_CODE=The provided language code is invalid. Currently, I know how to speak the following languages: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=I could not load the XML database named ''{0}''. I have no idea why it failed, though. Perhaps the file was moved or deleted before or during the reading operation. Or maybe I do not have the proper permissions to read the file. By the way, make sure the XML file is well-formed.
ERROR_PARSER_INVALID_PREAMBLE=I am sorry, but the preamble ''{0}'' could not be found. Please make sure this key exists in the configuration file.
@@ -110,6 +111,7 @@ ERROR_VELOCITY_IO_EXCEPTION=The template engine was not able to write the output
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=There are more details available on this exception:
INFO_DISPLAY_EXECUTION_TIME=Total: {0} seconds
INFO_DISPLAY_FILE_INFORMATION=Processing ''{0}'' (size: {1}, last modified: {2}), please wait.
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Although executing in dry-run mode, this entry might be already processed since it returned a boolean value: {0}
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=About to run: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Although executing in dry-run mode, this entry is always processed since it is a trigger. Note that the effects of a trigger might influence the current execution.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=This entry is a trigger originated from the rule scope. Note that the effects of a trigger might influence the current execution.
@@ -136,6 +138,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=set the execution timeout (in milliseconds)
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=print the command output
INFO_PARSER_VERSION_DESCRIPTION=print the application version
LOG_INFO_BEGIN_BUFFER=BEGIN OUTPUT BUFFER
+LOG_INFO_BOOLEAN_MODE=Boolean value: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIRECTIVES
LOG_INFO_END_BUFFER=END OUTPUT BUFFER
LOG_INFO_INTERPRET_RULE=I am ready to interpret rule ''{0}''.
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en_QN.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en_QN.properties
index db583d4669..c9a2013d26 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en_QN.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_en_QN.properties
@@ -64,6 +64,7 @@ ERROR_INTERPRETER_NULL_COMMAND=Thass a rum ole dew but one onnem commands have h
ERROR_INTERPRETER_RULE_NOT_FOUND=Thass a rum ole dew but there ent no ''{0}'' in any onnem rule paths. Praps you ent spelled that right. I coont find ''{0}.yaml'' in any onner paths: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=Atwin me, yew an'' the geartepost I ent got no idear abowt these keys in the directive: {0}. Howsomever, dunt you git yarself inta a rite ole puckaterry. Do you jist hull them outta yar map.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=Wuh, ole partner, that 'exit' expression ent givin' me a yis or no answer. Thass allus got to dew that even if there ent nuffin else to dew. Howsomever, dunt you git yarself inta a rite ole puckaterry, dew you jist tricolate the return statement and try agin.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=The ''isSubdirectory'' method requires a directory, not a file. It looks like ''{0}'' does not appear to be a directory at all.
ERROR_LANGUAGE_INVALID_CODE=Cor blast me, my bewty, but you hully copped me there wi'' that language code. I can ony mardle in these languages: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=Cor blast me, ole partner, but that XML database ''{0}'' ent half puttin'' on its parts but I ent got no idear wass gone wrong. Praps the file was hulled abowt afore or time the reading operation was doing else maybe I''re gotta he''sum proper permissions to snout abowt the file. Atwin yew, me an'' the geartepost, do yew make sure the XML is in good kelter.
ERROR_PARSER_INVALID_PREAMBLE=Thass a rum ole dew, ole partner, but I can''t find the preamble ''{0}''. Do yew make sure that key exist in the configuration file.
@@ -111,6 +112,7 @@ ERROR_VELOCITY_IO_EXCEPTION=That ent gorn right, my bewty. The template engine w
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=Hear's orl my know on that aggraweartin' exception:
INFO_DISPLAY_EXECUTION_TIME=Wuh that took {0} seconds but if thass a slight longer than you expected, dunt yew go mobbing me abowt it cors that ent my fault. My grandf''ar dint have none of these pearks. He had to use a pen and a bit o'' pearper, but thass bin nice mardling wi'' yew. Dew yew keep a troshin''!
INFO_DISPLAY_FILE_INFORMATION=Hold yew hard, ole partner, I''m gornta hev a look at ''{0}'' (thass {1} big, that is, and that was last chearnged on {2} in case yew dunt remember).
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Although executing in dry-run mode, this entry might be already processed since it returned a boolean value: {0}
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=This is what I''m abowt to dew: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Wuh, ole partner, I know this is a dry-run, but this entry has gorta be done cos thass a trigger. Thass hully important yew should know that might doss things on the huh.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=Wuh, ole partner, this entry is one onem triggers what come from the rule scope. Thass hully important yew should know that might put this jarb hully on the huh.
@@ -137,6 +139,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=wuh, yew dunt want them system commands to run o
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=thass dew you want ter system commands to hav' a mardle wi'yew an'orl
INFO_PARSER_VERSION_DESCRIPTION=dew yew use this dew you want my know abowt this version
LOG_INFO_BEGIN_BUFFER=BEGIN OUTPUT BUFFER
+LOG_INFO_BOOLEAN_MODE=Boolean value: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIRECTIVES
LOG_INFO_END_BUFFER=END OUTPUT BUFFER
LOG_INFO_INTERPRET_RULE=I''m orl ready, ole parter, to dew the rule ''{0}''.
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_it.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_it.properties
index 70afb93ec6..1f32907fbd 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_it.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_it.properties
@@ -63,6 +63,7 @@ ERROR_INTERPRETER_NULL_COMMAND=Sono spiacente, ma a quanto pare il risultato di
ERROR_INTERPRETER_RULE_NOT_FOUND=Non sono riuscito a trovare una regola chiamata ''{0}'' nei percorsi per le regole impostati. Forse una parola scritta sbagliata? Stavo cercando un file con il nome ''{0}.yaml'' nei seguenti percorsi in ordine di priorità: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=Ho trovato queste chiavi sconosciute nella direttiva: {0}. Dovrebbbe essere facile correggere, toglile dalla mappa.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=L'espressione di 'uscita' deve essere sempre un valore booleano (anche se non c'è alcun calcolo nella parte di chiusura). Dovrebbe essere facile correggere: assicurati che l'asserzione del 'type return' sia giusta e riprova.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=Il metodo ''isSubdirectory'' richiede una directory, non un file. Sembra proprio che ''{0}'' non sia una directory.
ERROR_LANGUAGE_INVALID_CODE=La lingua richiesta non è valida. Al momento, so parlare le seguenti lingue: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=Non ho potuto caricare il database XML di nome ''{0}''. Purtroppo non ho idea del perché sia andata male. Forse il file è stato spostato o cancellato prima o durante l''operazione di lettura. O forse non ho i permessi necessari per leggere il file. Già che ci siamo, assicurati che il file XML sia ben formato.
ERROR_PARSER_INVALID_PREAMBLE=Mi dispiace, ma non è stato possibile trovare il preambolo ''{0}''. Assicurati che questa chiave esista nel file di configurazione.
@@ -110,6 +111,7 @@ ERROR_VELOCITY_IO_EXCEPTION=Il motore per i 'template' non è riuscito a scriver
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=Ci sono altri dettagli riguardo a questa eccezione:
INFO_DISPLAY_EXECUTION_TIME=Totale: {0} secondi
INFO_DISPLAY_FILE_INFORMATION=Elaborazione ''{0}'' (totale: {1}, modificato il: {2}), attendere.
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Sebbene stia eseguendo in modo ''dry-run'', questo elemento potrebbe essere già stato elaborato, perché ha restituito un valore booleano: {0}
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=Sto per lanciare: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Sebbene stia eseguendo in modo 'dry-run', questo elemento è sempre elaborato perché è un 'trigger'. Nota che gli effetti di un 'trigger' possono influenzare l'esecuzione.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=Questo elemento è un 'trigger' generato nell'ambito della regola. Nota che gli effetti di un 'trigger' possono influenzare l'esecuzione.
@@ -136,6 +138,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=imposta il timeout di esecuzione (in millisecond
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=mostra l'outout del comando
INFO_PARSER_VERSION_DESCRIPTION=mostra la versione dell'applicazione
LOG_INFO_BEGIN_BUFFER=BEGIN OUTPUT BUFFER
+LOG_INFO_BOOLEAN_MODE=Valore booleano: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIRECTIVES
LOG_INFO_END_BUFFER=END OUTPUT BUFFER
LOG_INFO_INTERPRET_RULE=Sono pronto a interpretare la regola ''{0}''.
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_nl.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_nl.properties
index 9403078b98..6aa6afa6c6 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_nl.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_nl.properties
@@ -63,6 +63,7 @@ ERROR_INTERPRETER_NULL_COMMAND=Het spijt me, maar een van de opgegeven opdrachte
ERROR_INTERPRETER_RULE_NOT_FOUND=Ik kon de regel met de naam ''{0}'' niet vinden in de opgegeven regelpaden. Misschien een spelfout? Ik heb geprobeerd het bestand ''{0}.yaml'' te vinden in de volgende paden in volgorde van prioriteit: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=Ik heb de volgende onbekende verwijzingen gevonden in de directive: {0}. Dit zou makkelijk op te lossen moeten zijn: verwijder deze uit de verwijzingstabel.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=De 'exit'-expressie moet altijd een boolean waarde teruggeven (zelfs als er geen berekening heeft plaatsgevonden). Dit zou makkelijk op te lossen moeten zijn: pas het type van de return-regel aan en probeer het opnieuw.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=De ''isSubdirectory''-methode vereist een mapje, geen bestand. Het lijkt erop dat ''{0}'' geen mapje is.
ERROR_LANGUAGE_INVALID_CODE=De opgegeven taalcode is ongeldig. Op het moment accepteer ik de volgende talen: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=Ik kon de XML-database met de naam ''{0}'' niet laden. Ik weet niet waarom het precies fout ging. Misschien was het bestand verplaatst of verwijderd tijdens de leesoperatie. Of misschien heb ik niet de juiste rechten om het bestand te lezen. Overigens: zorg ervoor dat het XML-bestand welgevormd is.
ERROR_PARSER_INVALID_PREAMBLE=Het spijt me, maar de preamble ''{0}'' is niet gevonden. Zorg ervoor dat deze verwijzing bestaat in het configuratiebestand.
@@ -110,6 +111,7 @@ ERROR_VELOCITY_IO_EXCEPTION=De template-verwerking kon niet naar het uitvoerbest
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=Er zijn meer details beschikbaar voor deze exception:
INFO_DISPLAY_EXECUTION_TIME=Totaal: {0} seconden
INFO_DISPLAY_FILE_INFORMATION=Verwerken van ''{0}'' (grootte: {1}, laatst gewijzigd: {2}), een ogenblik geduld.
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Ondanks het uitvoeren in dry-runmodus is dit item mogelijk al verwerkt omdat het de booleaanse waarde terug heeft gegeven: {0}
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=Begin met uitvoeren: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Ondanks het uitvoeren in dry-runmodus wordt dit onderdeel altijd uitgevoerd omdat het een trigger is. Merk op dat de effecten van een trigger de huidige uitvoering kunnen beïnvloeden.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=Dit onderdeel is een trigger die binnen het bereik van de regel valt. Merk op dat de effecten van een trigger de huidige uitvoering kunnen beïnvloeden.
@@ -136,6 +138,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=stel de maximale uitvoeringsduur in (in millisec
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=toon de opdrachtuitvoer
INFO_PARSER_VERSION_DESCRIPTION=toon de applicatieversie
LOG_INFO_BEGIN_BUFFER=OPEN UITVOER
+LOG_INFO_BOOLEAN_MODE=Booleaanse waarde: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIRECTIVES
LOG_INFO_END_BUFFER=SLUIT UITVOER
LOG_INFO_INTERPRET_RULE=Ik ben klaar om regel ''{0}'' te verwerken.
diff --git a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_pt_BR.properties b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_pt_BR.properties
index 272a2f3ce9..3ce8cd2fb6 100644
--- a/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_pt_BR.properties
+++ b/support/arara/source/src/main/resources/com/github/cereda/arara/localization/messages_pt_BR.properties
@@ -63,6 +63,7 @@ ERROR_INTERPRETER_NULL_COMMAND=Sinto muito, mas, aparentemente, um dos comandos
ERROR_INTERPRETER_RULE_NOT_FOUND=Não consegui encontrar uma regra chamada ''{0}'' nos caminhos de regras especificados. Talvez uma palavra digitada incorretamente? Eu estava procurando por um arquivo chamado ''{0}.yaml'' nos seguintes caminhos, em ordem de prioridade: {1}
ERROR_INTERPRETER_UNKNOWN_KEYS=Encontrei as seguintes chaves desconhecidas na diretiva: {0}. Isso é fácil de resolver, apenas remova essas chaves do seu mapa.
ERROR_INTERPRETER_WRONG_EXIT_CLOSURE_RETURN=A expressão 'exit' referente ao código de saída deve sempre retornar um valor lógico (mesmo se não há computação propriamente dita). Isso é fácil de resolver: apenas certifique-se de corrigir o tipo de retorno e tente novamente.
+ERROR_ISSUBDIRECTORY_NOT_A_DIRECTORY=O método ''isSubdirectory'' requer um diretório, não um arquivo. Observe que ''{0}'' não parece ser um diretório.
ERROR_LANGUAGE_INVALID_CODE=O código de idioma especificado é inválido. No momento, eu sei falar os seguintes idiomas: {0}
ERROR_LOAD_COULD_NOT_LOAD_XML=Não consegui carregar o banco de dados XML chamado ''{0}''. Não tenho ideia porque não deu certo. Talvez o arquivo tenha sido movido ou removido antes ou durante a operação de leitura. Ou talvez eu não tenha as permissões corretas para leitura do arquivo. A propósito, certifique-se de que o arquivo XML esteja correto.
ERROR_PARSER_INVALID_PREAMBLE=Sinto muito, mas o preâmbulo ''{0}'' não foi encontrado. Por favor, certifique-se de que esta chave existe no arquivo de configuração.
@@ -110,6 +111,7 @@ ERROR_VELOCITY_IO_EXCEPTION=O motor de modelo não conseguiu escrever no arquivo
INFO_DISPLAY_EXCEPTION_MORE_DETAILS=Detalhes adicionais estão disponíveis para esta exceção:
INFO_DISPLAY_EXECUTION_TIME=Total: {0} segundos
INFO_DISPLAY_FILE_INFORMATION=Processando ''{0}'' (tamanho: {1}, última modificação: {2}), por favor, aguarde.
+INFO_INTERPRETER_DRYRUN_MODE_BOOLEAN_MODE=Apesar da execução em modo dry-run, é provável que esta entrada já foi processada, dado que o seguinte valor lógico foi retornado: {0}
INFO_INTERPRETER_DRYRUN_MODE_SYSTEM_COMMAND=A executar: {0}
INFO_INTERPRETER_DRYRUN_MODE_TRIGGER_MODE=Apesar da execução em modo dry-run, esta entrada é sempre processada por tratar-se de um gatilho. Observe que os efeitos de um gatilho podem influenciar a execução corrente.
INFO_INTERPRETER_VERBOSE_MODE_TRIGGER_MODE=Esta entrada é um gatilho originado a partir do escopo da regra. Observe que os efeitos de um gatilho podem influenciar a execução corrente.
@@ -136,6 +138,7 @@ INFO_PARSER_TIMEOUT_DESCRIPTION=define o timeout de execução (em milissegundos
INFO_PARSER_VERBOSE_MODE_DESCRIPTION=imprime a saída do comando
INFO_PARSER_VERSION_DESCRIPTION=imprime a versão da aplicação
LOG_INFO_BEGIN_BUFFER=INÍCIO DO BUFFER DE SAÍDA
+LOG_INFO_BOOLEAN_MODE=Valor lógico: {0}
LOG_INFO_DIRECTIVES_BLOCK=DIRETIVAS
LOG_INFO_END_BUFFER=FINAL DO BUFFER DE SAÍDA
LOG_INFO_INTERPRET_RULE=Estou pronto para interpretar a regra ''{0}''.