Comments (7)
well I'd tend to agree but @jwswj and I agreed that we need to show them the way to do it if they ever want to get their app localized
Let's keep the old format please...
from demo_apps.
I don't think it's a very hard thing to get value
& title
pairs set up.
We could just refer the developers to App Reference and let them decide which style they want to use.
from demo_apps.
Do we know how many public vs private apps are being created? It is basically us that create public apps right? So for private apps, it's not something the app developer really needs to know because they would be unlikely to internationalise their app. If the majority of apps would be private (and hence without translations), is it good to have examples of an app using something they wont use?
We can certainly document how internationalisation can be done in your en.json
but it should be an optional step in my opinion. The entire value
, title
key pairs are stripped down to the simply implementation when the app is served in installed.js
as well.
from demo_apps.
Private app authors will probably just hard code all the values in app.js
or *.hdbs
. 😄 like we tended to do (before being corrected)
from demo_apps.
My thinking was that we have our apps documentation (developer.zendesk.com) and existing sample apps and most of our public apps (if not all) still using the normal format en.json. And I think that format serves the majority of the public audience well. If we show this new format to the general public only for a very small portion of the audience and that small portion probably know this already, the most of public people will get confused because the json file doesn't tell much what's that structure for. I can think of 3 options:
- Don't show this new format to general public.
- Show this new format to general public, but update our documentation to explain 2 different translation formats, and update our public apps and/or existing sample apps to use this new format.
- Only allow new translation format. This also needs to update documentation and existing apps.
I like option 1.
from demo_apps.
Thanks guys for opening this discussion but we need to go with option 2
We have to show the "example" to our App developers, get them to understand the importance of our other markets.
Half of zendesk customers core language isn't english. We get a public app submission a week so the math is pretty simple to do
from demo_apps.
Agree that option 2 is what we need to do.
On Sat, Dec 21, 2013 at 12:02 PM, Maxime Prades [email protected]:
Thanks guys for opening this discussion but we need to go with option 2
We have to show the "example" to our App developers, get them to
understand the importance of our other markets.Half of zendesk customers core language isn't english. We get a public app
submission a week so the math is pretty simple to do—
Reply to this email directly or view it on GitHubhttps://github.com//issues/16#issuecomment-31071015
.
Jason Smale
Engineering Director - APAC
Zendesk http://www.zendesk.com/
Twitter: @jwswj | Skype: zendesk.jsmale | Phone: +61 402 073 344
from demo_apps.
Related Issues (16)
- How to use Zendesk Garden React components HOT 1
- Error when creating notely event HOT 3
- Each app in its own folder HOT 1
- Dead link on readme
- Listening for postMessage HOT 3
- Update iFrame Sample App HOT 3
- Example for Ember app integration? HOT 4
- Error on Plugin Jquery - Autocomplete HOT 3
- Find one "input" custom for implemention autocomplete
- www.teachmyapi.com is down HOT 3
- Question : We need to use postMessage API and want to use window Obj HOT 9
- JWT with CORS? HOT 3
- Hiding top-bar application on clicking outside of application HOT 3
- The V2 demo apps do not include source files HOT 1
- looking for channel_integrations demo, i try but it error with error creating requirements
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from demo_apps.