Skip to content
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

Open
5 of 6 tasks
eprovst opened this issue Jan 12, 2018 · 11 comments
Open
5 of 6 tasks

Better language support #6

eprovst opened this issue Jan 12, 2018 · 11 comments

Comments

@eprovst
Copy link
Owner

eprovst commented Jan 12, 2018

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.

  • English
  • French (might need correcting, slightly incomplete)
  • Dutch
  • German
  • Italian
  • More to come...
@johannschopplich
Copy link
Contributor

johannschopplich commented Jan 12, 2018

Being able to completely localize a script—including tags—is just lovely.

German

  • Scene tag: Szene
  • Transition tag: ZU:
  • Act tag: AKT
  • End of act tag: ENDE DES AKTS as well as the variation ENDE DES AKTES
  • More tag: (MEHR)
  • cont'd tag: (fortges.)
  • Scene headings: INT., EXT., INT./EXT., I/E and ETABL. (etablierend)

P.S.: Those are correct translations. 😃
Edit: Updated translation.

@eprovst
Copy link
Owner Author

eprovst commented Jan 13, 2018

@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 😄

@johannschopplich
Copy link
Contributor

@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.

@eprovst
Copy link
Owner Author

eprovst commented Jan 13, 2018

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') 🙂

@johannschopplich
Copy link
Contributor

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.

@johannschopplich
Copy link
Contributor

@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?

@eprovst
Copy link
Owner Author

eprovst commented Jan 16, 2018

(cont'd)'s use should maybe be explained a bit more, (cont'd) and (MORE) are inserted by Wrap PDF when there is a pagebreak in the middle of dialogue, it has no meaning in Fountain nor in the Wrap format.

So which one do you think reflects this use best? (fortges.) or (weiter)? 🙂

@johannschopplich
Copy link
Contributor

johannschopplich commented Jan 16, 2018

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 (fortges.) absolutely is the choice here! 👍

(So forget I mentioned this. 😉)

@eprovst
Copy link
Owner Author

eprovst commented Jan 19, 2018

Wraparound Languages has been integrated into Wraparound Parser and Wraparound PDF, making German available in the next release 😄

@johannschopplich
Copy link
Contributor

johannschopplich commented Jan 20, 2018

@ElecProg 👍
Looking forward to trying it out!

@eprovst
Copy link
Owner Author

eprovst commented Jan 31, 2018

@jschopplich Because of the name change, quick note: German is available in the current release 😄

@eprovst eprovst removed this from the Longterm Goals milestone Sep 18, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants