lokalized/lokalized-java

Issues

• Placeholders should still be interpolated if no translation found

  #18 opened 7 years ago by revetkn
  0

• No Support for Klingon

  #17 opened 7 years ago by walkingonwires
  0

• Ensure tests cover common error cases

  #7 opened 7 years ago by revetkn
  0

• Finalize documentation

  #6 opened 7 years ago by revetkn
  0

• Finalize lokalized.com

  #14 opened 7 years ago by revetkn
  0

• Provide static analysis tool to generate/maintain localized strings files

  #2 opened 7 years ago by revetkn
  1

• Alternative expressions should support a range construct

  #16 opened 7 years ago by revetkn
  0

• If a strings file is missing language form translations, warn/error on load

  #15 opened 7 years ago by revetkn
  0

• Support for cardinal ranges

  #12 opened 7 years ago by revetkn
  2

• Support for ordinals (1st, 2nd, 3rd, 4th, ...)

  #8 opened 7 years ago by revetkn
  2

• Finalize Plural Cardinality rules for initial release

  #9 opened 7 years ago by revetkn
  2

• Finalize Plural Ordinality rules for initial release

  #11 opened 7 years ago by revetkn
  1

• Localized strings files should support "available context" construct to facilitate tooling

  #13 opened 7 years ago by revetkn
  0

• For tooling, placeholders should support a type hint

  #10 opened 7 years ago by revetkn
  0

• Finalize support for LanguageRange in DefaultStrings

  #5 opened 7 years ago by revetkn
  1

• Missing values should leave placeholders intact

  #1 opened 7 years ago by revetkn
  0

• Permit placeholder '{{' escaping

  #4 opened 7 years ago by revetkn
  0

• Wire in alternatives expression evaluator

  #3 opened 7 years ago by revetkn
  1