hi there
does it have open-source native mobile apps?
No, but getting Cordova builds working is a future goal.
reactioncommerce/reaction#1213
Just not a near future goal a this point.
reactioncommerce/reaction#1213
Just not a near future goal a this point.
Also see https://guide.meteor.com/mobile.html
If you decide to try to get things working, we’d be happy to accept contributions.
@jshimko
meteor npm install authorize-net@github:ongoworks/node-authorize-net not working on windows 10
error: cannot spawn sh: No such file or directory
wonderful
how to disable the authorize.net package just in case.
would you mind filing an issue with all of your error details?
will do
thank you
you can comment out the
client/index.js and server/index.js in that plugin
and remove the npm package from the package.json
(until it’s fixed)
will do thanks
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:05
Hello there
I am working on translating the interface
@hbakhtiyor Yep, sure does. Right there in the “Future” section. ;)
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:06
using i18n-translate npm
any suggestions for languages of interest ?
I can do some now
or, if req, I can redo existing ones if there are doubts on their status
that’s probably a question for @aaronjudd
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:08
I find i18n-translate npm great, ( it requires google translate api , but not that expensive).
looking at the file sizes, english is way much bigger than all the rest, which means were done manually probably...
that’s definitely the case
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:17
I need small help with the format:
"error": {
"nameRequired": "Este necesar numele.",
"isRequired": "{{Câmpul este obligatoriu.",
"mustBeNumber": "{{}} Câmp trebuie să fie un număr.",
"variantFieldIsRequired": "Varianta {{număr}} {{}} câmp este necesar."
}
while original is:
"error": {
"nameRequired": "Name is required.",
"isRequired": "{{field}} is required.",
"mustBeNumber": "{{field}} must be a number.",
"variantFieldIsRequired": "Variant {{number}} {{field}} is required."
}
"error": {
"nameRequired": "Este necesar numele.",
"isRequired": "{{Câmpul este obligatoriu.",
"mustBeNumber": "{{}} Câmp trebuie să fie un număr.",
"variantFieldIsRequired": "Varianta {{număr}} {{}} câmp este necesar."
}
while original is:
"error": {
"nameRequired": "Name is required.",
"isRequired": "{{field}} is required.",
"mustBeNumber": "{{field}} must be a number.",
"variantFieldIsRequired": "Variant {{number}} {{field}} is required."
}
are "field" and "number" keywords which should not be translated?
I think you need to leave {{field}} and {{number}} as is
yes, those are variables
changing them will break them
For example, here’s a tranlation with a
https://github.com/reactioncommerce/reaction/blob/d569c68747a184a71c07c1e3e6ef0f48b525cd57/imports/plugins/core/ui/client/templates/dashboard/dashboard.js#L39-L41
defaultValue variable passed inhttps://github.com/reactioncommerce/reaction/blob/d569c68747a184a71c07c1e3e6ef0f48b525cd57/imports/plugins/core/ui/client/templates/dashboard/dashboard.js#L39-L41
nevermind, bad example. defaultValue is just that.
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:22
I will translate only in 3-4 languages like ro, el, ru, fr ; I can trasnlate others when there will be a more finalized version (ping/email me when you consider it so)
if you find other langs. important now, let me know
are you just using Google Translate or do you actually speak them?
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:22
google :)
I only speak ro from the list :)
I’d ask @aaronjudd before spending too much effort. I’ve personally seen some hilariously terrible translation results from Google and we don’t want to add bad translations. We generally prefer native speakers to contribute them.
Because we’d have no other way to know if they were wrong
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 19:24
I guess natives can fix the delta instead of doing monkey job
@jshimko instead of
meteor npm install when I did npm install authorize-net@github:ongoworks/node-authorize-net it worked. So could be the npm issue. meteor npm -v is 3.10.6 and npm -v is 3.10.3. I think I am the only one affected, suggest let us not spend time on it.
ok. thanks for the update
@EpifaniaCollection we’re going to be automatically converting these with paid translations. We’re testing Qordoba.com, LingoHub.com and Transifex right now -> we have active projects setup up in each these systems, but they’re all presenting some level of challenge. We’re tracking this in #1111.
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 20:16
I am trying google translate API via i18n-translate npm (it understands the json format).
indeed, there is quite some after the automated translation... but the funny translations make you smile while correcting :)
these will not be (for the most part) machine translations, but actual translations done by translators… so that hopefully we get the right words/tone
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 20:18
ok. I am manually correcting and hopefully soon submitting .ro only
if you want to submit a PR, I suggest doing it only for the language(s) that you speak, and that make sense to complete an existing translation file.. Russian, Chinese for instance are community contributed, and so the existing translations won’t be updated, but rather the missing translations in those files will be translated from the en.json
these tools that I’m testing also have automating and the ability to add contributors as “translators”, so once I’ve got it working, we’ll be able to manage future translations a little easier ( with access to another tool)
so I guess the take away is.. if you contribute something that doesn’t make sense (some weird google translation), that may not be corrected when we have the translators work on them.. because they’ll be ignoring existing translated strings
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 20:22
is there a way to merge the en.json with xx.json and create an xx_new.json in order for the contributor to translate the new fields ?
I don’t have an easy way to do that.. but I bet you could use some merge/diff tool to do that...
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 20:23
or, ideally get the xx_delta.json, with the new fields only, and afterward merge the xx_old.json with xx_new.json ?
the services I’m testing all do that "auto-magically"
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 20:24
ok :)
if you leave a comment for me on #1111 I can invite you to the translation service, once I’ve picked one.
right now, I’m back to using Transifex, as I’m blocked on LingoHub and Qordoba
Epifania Collection - christian orthodox priest vestments and church items
@EpifaniaCollection
Sep 22 2016 20:31
funny to see that google's API translate "Analytics" to "Google Analytics" =)
that’s so Google