c6168be8b1
* Tag Search + Tests + Search slight refactor First commit improving search. Different struct have their own file with their tests. This way of separating struct by files is inspired by the go packages I've seen so far. Added new behaviour as discussed in #1334 * fix fallback to ES * Added some comments to explain PG fallback + log err moved * Refactored search Nearly fully covered WhereParams struct has disappeared for Query struct instead In DB model, we use an interface implementing Query struct methods * 1rst Refactor of Tags (WTF already?!) Prepare Tags for the refactored system. Now there will be descriptive tags for a particular release (ecchi, BDSM, ....) and typed tags. Typed tags are tags relevant to all torrents and can be limited to some input value. For example, video quality is a typed tag limited to some values (hd, full hd, sd, ...). In the same way, anidbid is also a typed tag but doesn't have default values. Furthermore, the location storage of tags have changed, now accepted descriptive tags are stored in the torrents table in the column "tags" and they are separated by commas. In the opposite, accepted typed tags can have have their own column in the torrents table. For example, anidbid, vndbid will populate the column DbID when accepted. On the other hand, videoquality will populate the same way as descriptive tags. This behaviour depends on the callbackOnType function in tag/helpers.go * fix for modtools :') * Added anidb, vndb, dlsite & vmdb id fields in torrent model. Tags don't have an accepted field anymore. Accepted Tags are in torrent.AcceptedTags and non-accepted ones in torrrent.Tags. New Helper + New Changelog for translation string. * New upload/edit form for torrent tags. Now the inputs are dynamically generated by the helper tag_form. No more modal window in those form, only inputs. Support of tags in API New translation string for the link to the modal on torrent view. More comments in the functions for tags * Improving how config for tags work. Adding a test on them with understandable messages. Config for tags have now a Field attribute which is linked to the Torrent model. For example anidbid tag type has now a AnidbID field in config which is the name of the field in torrent model (AnidbID). Every new tag type need to have a field attribute with its counterpart in torrent Model. Fixing some errors * Fix compile error + Tests Errors * Improve performance by caching the list of tags with an index Adding/removing tags works/tested New translation strings TODO: test/fix adding tag on upload/edit * Mini fix to display video quality + tags works/tested on modo edit * Fix editing tags on modpanel * Edit tags works * Add translation string * Add search backend for tags. ?tags=xxx,eee,ddd ?anidb=21 ?vndb=23 ?vgmdb=24 ?vq=full_hd * Fix Ajax tag Removal&Add * Added form for descriptive tags * Forgot to add the link between database and form for descriptive tags. * Adding the increase/decrease pantsu for descriptive tags * Fix #1370 * When you actually forgot to commit files after having forgotten commits |
||
|---|---|---|
| .. | ||
| ca-es.json | ||
| CHANGELOG.md | ||
| de-de.all.json | ||
| en-us.all.json | ||
| es-es.all.json | ||
| fr-fr.all.json | ||
| hu-hu.all.json | ||
| in-id.all.json | ||
| is-is.all.json | ||
| it-it.all.json | ||
| ja-jp.all.json | ||
| ko-kr.all.json | ||
| nb-no.all.json | ||
| nl-nl.all.json | ||
| pt-br.all.json | ||
| pt-pt.all.json | ||
| README.md | ||
| ro-ro.all.json | ||
| ru-ru.all.json | ||
| sv-se.all.json | ||
| th-th.all.json | ||
| zh-cn.all.json | ||
| zh-tw.all.json | ||
Contributing to translation
You can add your own language support or edit it easily to the website.
Add a language
To add a language you need to copy /translations/en-us.all.json and translate the strings beside the "translation" key. Do not edit "id" which is the id used to display the translation.
You can also, if you have the website installed, create an empty languageCode.all.json (eg. en-us.all.json) and use the following command:
cd translations && goi18n -flat false en-us.all.json languageCode.all.json you need to replace languageCode with the actual language code (eg. en-us)
A new file languageCode.untranslated.json will be created with the new translation strings. Translate them and when it's done, run the following command:
goi18n -flat=false en-us.all.json languageCode.all.json languageCode.untranslated.json you need to replace languageCode with the actual language code (eg. en-us)
After creating a new translation, create a new translation string inside "en-us.all.json", like the following:
...
},
{
"id": "language_(languageCode)_name",
"translation": "(your language name, in English)"
},
...
where languageCode is the newly created ISO code (eg. ja-jp, pt-br).
Before pulling, be sure to delete .unstranslated.json file
Edit a language
To edit a language you can keep tracking of new strings added to en-us.all.json with the use of git and add the new strings manually to your file.
Or you can also, if you have the website installed, use the following command:
cd translations && goi18n -flat false en-us.all.json languageCode.all.json you need to replace languageCode with the actual language code (eg. en-us)
A new file languageCode.untranslated.json will be created with the new translation strings. Translate them and when it's done, run the following command:
goi18n -flat=false en-us.all.json languageCode.all.json languageCode.untranslated.json you need to replace languageCode with the actual language code (eg. en-us)
Before pulling, be sure to delete .unstranslated.json file