-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tutorial/API Docs issues #120
Comments
While I understand it may take a little time to investigate these issues, I'd be most appreciative for a clarification now about the differences between the seemingly overlapping projects (and overlapping APIs), fluent-web (which isn't referenced on the main README), fluent-dom, and the separate l20n.js project (which incidentally sees like it should be dependent on fluent-dom but isn't). Is fluent-web meant to take over the role of l20n.js? I'd rather not be digging into the code of, or making PRs for, a project you're deprecating... |
@brettz9 Thank you so much for the thorough review of the documentation! There sure is a lot of room for improvement :) I'll be working this week and next week on addressing the issues you've found. To answer the questions from your second comment: yes, |
No worries--these were mostly small recommendations, and I am quite eager to see the web community (including myself) benefit from what appears to me to be such a very well thought out, experience-driven and comprehensive framework.... Thank you all for your hard work! |
Any chance of reviewing these? |
Assigning stas since he started reviewing it already. :) |
who can tell me fluentjs tutorial? i don't understanding how to use fluent in my web project! |
@anlexN : No, there is a framework for it though it defines a file format . For the framework, see especially https://github.com/projectfluent/fluent.js/tree/master/fluent . For the format of the file, see https://projectfluent.org/fluent/guide/ and https://projectfluent.org/play/ @stasm : Any chance of a review? Also, FYI, I've added a new item at no. 11 suggesting Terms mention their possible use for Unicode (like how XML entities can be used). |
From my review of the tutorial and API docs:
hourCycle
Fluent.NumberArgument
to instead useIntl.MessageNumberArgument
DOMLocalization
orLocalization
such as is within https://github.com/l20n/l20n.js/blob/master/docs/dom_localization.md and https://github.com/l20n/l20n.js/blob/master/docs/localization.md -- which would be nice to have available from fluent-dom.fluent-web
(which isn't referenced on the main README),fluent-dom
, and the separatel20n.js
project (which incidentally sees like it should be dependent onfluent-dom
but isn't).MessageArgument
,MessageNumberArgument
, andMessageDateTimeArgument
) for use as part of partial arguments withinformat
(if not the other exports,mapContextSync
andCachedIterable
) since looking through the API docs alone didn't make this apparent. If l20n.js' use ofList
(apparentlyIntl.ListFormat
) as referenced at http://l20n.org/learn/builtins is also available, it would be nice to have this documented.|
for message line breaks is also available in fluent.js, it is not documented as such at http://projectfluent.org/fluent/guide/text.html (as it is at http://l20n.org/learn/working-with-text-multiline-interpolation ). (And if it isn't, I think it should be drawn out as a special feature of l10n)LEN
as documented http://l20n.org/learn/advanced-selectors is also available in fluent.js, it is not documented at http://projectfluent.org/fluent/guide/functions.html#built-in-functions (and if it isn't, I think it should be drawn out as a special feature of l10n). AlsoTAKE
is mentioned in the example code at http://l20n.org/learn/complex-example without detailed explanation there, and it is not clear whether it is available by default through l20n.js or through fluent.js. (Moreover, http://l20n.org/learn/complex-example is surfacing aTypeError
on the page but as there is no issue tracker for https://github.com/l20n/l20n.js I can't report it there.)new Localization
should instead benew DOMLocalization
and the first is missing the required second argument.-ellipsis
,-copyright
, etc. for these symbols if repeating their use, with the use of Terms here designating they were just local definitions perhaps set up by the translator for their own convenience.The text was updated successfully, but these errors were encountered: