-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Checked translation #581
base: dev
Are you sure you want to change the base?
Checked translation #581
Conversation
Problems running development in docker facebookarchive#534
* Remove NodeJS-Legacy (Fixes: facebookarchive#550) * Updated version of node.js installed to fix critical provisioning errors. By default, Ubuntu 14.04 uses a legacy version of node.js. This code removes the legacy version and updates to a newer version. * Source: https://nodejs.org/en/download/package-manager/#debian-and-ubuntu-based-linux-distributions * This PR fixes the provision/build issue from facebookarchive#550
…ixes: facebookarchive#554) (facebookarchive#555) * Downgraded Dropkick.js to version 2.1.10. The project originally was built using 2.1.10 and specified a near version in the 2.x.x release family. On August 27th 2017 Dropkick.js released version 2.2.0 which is incompatible with ES6 specs. The incompatibility with the new release of Dropkick.js caused the provisioning of the platform to fail. * Moved the installation process for Node.js to a function within `lib.sh`. This change streamlines the provision script. * Removed the installation of `wget` from provisioning. `wget` is no longer used within the project and is therefore unneeded. * Updated the `dl()` download function within the provision script to use `curl` exclusively, with retry options. The retry options are set to 5 retries with a 15-second delay between retries. The addition of the retry option ensures the provision can continue if there is a temporary issue with a remote connection or availability of a remote resource. * Added the `dl_pipe()` download function to the provision script. This download function provided the data from the remote resource via standard output to be piped into another command. As piping downloads within the provisioning process have become more common, this function streamlines the process. * Fixes facebookarchive#554 * Updates fixes for facebookarchive#550
* Updated links and information related to the installation process. * Included a link to Quick Setup Guide.
* Included message indicating that Pull Requests need to be submitted against `dev`. * Updated commands to branch from `dev`.
Na página de gerenciamento de Logos, o ENABLE e DISABLE não estava sendo traduzidos
Atualização da tradução do projeto.
There are definitely some missing translations (even from English) based on new changes that didn't incorporate the corresponding translations. Quick note:
We generally try to stay away from translating dynamic items (and instead translate the source). We will go through the rest of the translations and review. Thank you for the contribution! |
justinwray, Oh sorry!! I couldn't find any other way to translate that. I tried to copy from countries management: Countries Management
Logo Management
I guess we should correct both, right? Like: if ($logo->getEnabled()) {
|
@@ -12,7 +12,25 @@ ARG CRT | |||
|
|||
WORKDIR $HOME | |||
COPY . $HOME | |||
<<<<<<< HEAD |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You have an unresolved merge conflict here
I checked if lang_en.php had all of application texts and added what was missing. I also noticed that some texts weren't being translated by "tr" function.
IMPORTANT 1: I could not translate texts inside fbct/src/static/js .
IMPORTANT 2: All translations need to be revised in order to add what was missing.