-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better language support #6
Comments
Being able to completely localize a script—including tags—is just lovely. German
P.S.: Those are correct translations. 😃 |
@jschopplich Thanks for the translations so far, I seem to have missed some to be translated text in the initial version of the issue (most notably translations of scene headings). If you were to be able to provide these (and any potential important details about German) we can start adding it towards the next release 😄 |
@ElecProg I updated the translation. Would be great to see it in the next release! What do you mean by potential important details? As of now all English tags can be drop-in-replaced by their German counterparts. |
Some languages have some unique exceptions. For instance in French you don't have to write accents on capital letters but it's also common practice to write them anyway (both case should then be supported). Another example are surnames in Scotland, you can't capitalize the 'Mc' or 'Mac' (so one of the extensions of Wrap is to allow character names to begin with 'Mac' or 'Mc') 🙂 |
OK, got it. In German the genitive case of "Akt" is "Akt[e]s". The "e" is optional. Therefore Feltix should support both. I updated the translation sheet above. |
@ElecProg I thought about the German translation of cont'd a lot. It would be a good idea to let a second term be accepted—quite similar to the Dutch verder. Especially for faster writing one maybe prefer the simpler term "weiter"). I updated the translation sheet above. "(cont'd)": { "(fortges.)", "(weiter)" } Would you please add ↑ this here? |
So which one do you think reflects this use best? |
Ah okay. I searched around the interweb a bit, but sticked with thinking this tag can be used while writing, too. For being inserted automatically (So forget I mentioned this. 😉) |
Wraparound Languages has been integrated into Wraparound Parser and Wraparound PDF, making German available in the next release 😄 |
@ElecProg 👍 |
@jschopplich Because of the name change, quick note: German is available in the current release 😄 |
Description
One of the main reasons the Wrap extensions came to be was to better support scripts in different languages. However this has little effect when only three are supported: English, French and Dutch.
Of course different languages have different cultures and have different needs, however those where the screen- and stageplay tradition isn't too different from the Anglo-Saxon and Western-European world should be as much as possible be supported by the software.
Current translations and languages can be found here.
How can I help?
If you're able to provide translations of the following, you may comment them here and they (when correct) can be added to the program:
Scene tag: 'Scene'
Transition tag: 'TO:'
Act tag: 'ACT'
End of act tag: 'END OF ACT'
More tag: '(MORE)'
cont'd tag: '(CONT'D)'
Scene headings: 'INT.', 'EXT.', 'INT./EXT.', 'I/E' and 'EST.' (establishing).
If you are able to provide any extra notes on any peculiarities of your language, errors in current translations and/or possible aliases for the language metadata (eg. the name of your language in the language itself, etc.) these would also be most welcome.
Languages to be/already added
Note: these reflect the state of the Wrap Languages module, not the current release of Wrap.
The text was updated successfully, but these errors were encountered: