Valentyne Stigloher a68a4bad62 (de) show possessive articles by casus and genus in 3rd singular
dey/denen: no declension
die/denen: no declension
el/em: https://nibi.space/pronomen#el
em/em: https://nibi.space/pronomen#em, apparently no declension, even though inconsistent with el/em
en/en: https://geschlechtsneutral.net/pronomen/
en/em: https://geschlechtsneutral.net/pronomen/
ey/emm: language feeling, suffix of declensions feel easier
hie/hiem: language feeling, does not end on s so it gets declension; can't find source apart from 11db10955841ceaa2195d030689bf84ea9c0943a
et/siem: https://nibi.space/pronomen#et
hän/sim: https://nibi.space/pronomen#hän
hen/hem: https://nibi.space/pronomen#hen, apparently no declension
iks/iks: https://meinnamemeinpronomen.files.wordpress.com/2015/10/vorschau_layout_zine_2511.pdf, apparently no declension
ind/inde: https://nibi.space/pronomen#ind, different declension on genitiv
mensch/mensch: language feeling, rather long to get declension
nin/nim: https://www.geschlechtsneutral.com/lit/Liminalis-2008-Sylvain-Balzer.pdf
oj/ojm: https://frumble.de/blog/2021/03/26/ueberlegungen-zu-einer-genderneutralen-deutschen-grammatik/
per/per: https://nibi.space/pronomen#per
ser/sem: language feeling, short like per/per
sier/siem: https://www.annaheger.de/pronomen21/
xier/xiem: https://www.annaheger.de/pronomen33/
zet/zerm: https://nibi.space/pronomen#zzet, apparently no declension
er*sie/ihm*ihr: consistent with the double mention in seiner*ihrer, all possessive suffixes are doubled too
2023-11-09 19:25:41 +01:00
2023-11-06 20:47:47 +01:00
2023-10-07 14:21:08 +02:00
2023-08-22 19:07:44 +02:00
2023-07-06 18:32:25 +02:00
2023-07-04 22:36:18 +02:00
2023-08-21 19:23:54 +00:00
2022-06-25 16:40:20 +02:00
2023-05-15 17:43:23 +02:00
2023-08-21 19:23:54 +00:00

Zaimki.pl / Pronouns.page

Installation

git clone git@gitlab.com:PronounsPage/PronounsPage.git

We're using FontAwesome Pro, so to set up a local copy without having a FA license, open package.json and replace

"@fortawesome/fontawesome-pro": "git+ssh://git@gitlab.com:Avris/FontAwesomePro.git",

with

"@fortawesome/fontawesome-pro": "git+ssh://git@gitlab.com:Avris/FakeFontAwesomePro.git",

or, for Git via HTTPS:

"@fortawesome/fontawesome-pro": "git+https://git@gitlab.com/Avris/FakeFontAwesomePro.git",

Do not commit that change!

Build Setup

# install dependencies
$ make install

# configure environment
$ nano .env
$ make switch LANG=pl

# serve with hot reload at localhost:3000
$ make run

# build for production and launch server
$ make deploy
$ nuxt start

See LICENSE.

Development Documentation

Read this first.
When you add a new language, remember to modify the file ./locale/locales.js to add your language:


// Add an object according to the following format:
{code: 'xx', name: 'xx', url: 'https://xx.pronouns.page', published: false , symbol: 'x', family: 'xxx'}

// Setting 'published' to true means that the language was published onto the main site.
// For example: 
{code: 'pt', name: 'Português', url: 'https://pt.pronouns.page', published: true, symbol: 'ã', family: 'romance'}

If you're having problems using Yarn, npm is probably fine, but remember to switch any yarn [x] commands for npm run [x].
Remember to modify the .env file. You don't really need to set up any external APIs, just make up a secret.

// ...
SECRET=replaceThis
// ...

In order to test the login system, you can type in an email followed by a + (example@pronouns.page+). This way, you won't need a mailer, as the code will always be 999999. This feature is exclusive to development builds.

Windows

Current setup depends on working symlinks, which means that an NTFS filesystem is unfortunately required for Windows at the moment.

If you encounter a ParseError, make sure the file is in \n (Line Feed) mode instead of \r\n (Carriage Return Line Feed).

If you want to automate the change, try this.
Make sure that the .editorconfig looks like this:

[*.suml]
end_of_line = lf

Password

For unpublished locales and for the test server, a password is required to access the web interface. If you're on our Discord, you can ask for it there (or just use published: true for local development).

Troubleshooting

If you're having issues with HRM (Hot Module Replacement) not reloading automatically:

  • The modules within package.json are matching the repo's package.json.
  • nuxt.config.js has the following option:
watchers: {
    webpack: {
        aggregateTimeout: 300,
        poll: 1000
    }
}

Current translations being worked on

  • Catalan - @peiprjs
  • Hebrew - @ThatTransGirl
  • [Add yours!]
Description
No description provided
Readme 478 MiB
Languages
HTML 79.4%
TypeScript 10%
Vue 9.6%
SCSS 0.4%
Shell 0.3%
Other 0.3%