[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-02-14 Thread sba
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483


User sba changed the following:

What|Old value |New value

  Status|RESOLVED  |VERIFIED





--- Additional comments from s...@openoffice.org Mon Feb 14 16:47:01 + 
2011 ---
Verified in CWS locales34.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-02-08 Thread erack
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483


User erack changed the following:

What|Old value |New value

 Assigned to|erack |oc





--- Additional comments from er...@openoffice.org Tue Feb  8 22:24:24 + 
2011 ---
Reassigning to QA for verification.


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-29 Thread erack
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483


User erack changed the following:

What|Old value |New value

 Assigned to|ambershadow   |erack





--- Additional comments from er...@openoffice.org Sat Jan 29 22:38:33 + 
2011 ---
Grabbing issue.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-29 Thread erack
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483


User erack changed the following:

What|Old value |New value

  CC|'erack'   |''

  Status|NEW   |RESOLVED

  Issue type|TASK  |ENHANCEMENT

  Resolution|  |FIXED

Target milestone|---   |OOo 3.4





--- Additional comments from er...@openoffice.org Sat Jan 29 23:28:39 + 
2011 ---
sigh..

Warning: more than 1 character (2) in DateSeparator /  not supported by 
application.
Warning: more than 1 character (2) in ThousandSeparator ,  not supported by 
application.
Warning: more than 1 character (2) in DecimalSeparator .  not supported by 
application.
Warning: more than 1 character (2) in TimeSeparator :  not supported by 
application.
Warning: more than 1 character (2) in Time100SecSeparator :  not supported by 
application.
Warning: Time100SecSeparator equals TimeSeparator, this is probably an error.
Warning: Time100SecSeparator is different from DecimalSeparator, this may be 
correct or not. Intended?
Warning: Don't forget to adapt corresponding FormatCode elements when changing 
separators.
Error: DecimalSeparator not present in FormatCode formatindex=4.
Error: ThousandSeparator not present in FormatCode formatindex=4.
Warning: formatindex=4,44,45 are the only FormatCode elements checked for 
separator usage, there may be others that have errors.
Warning: FormatCode formatindex=12 for currency uses parentheses for negative 
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=13 for currency uses parentheses for negative 
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=14 for currency uses parentheses for negative 
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=15 for currency uses parentheses for negative 
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=17 for currency uses parentheses for negative 
amounts, which probably is not correct for locales not based on en_US.
Error: TimeSeparator not present in FormatCode formatindex=44.
Error: Time100SecSeparator not present in FormatCode formatindex=44.
Error: Time100SecSeparator+00 not present in FormatCode formatindex=44.
Warning: formatindex=4,44,45 are the only FormatCode elements checked for 
separator usage, there may be others that have errors.
Error: TimeSeparator not present in FormatCode formatindex=45.
Error: Time100SecSeparator not present in FormatCode formatindex=45.
Error: Time100SecSeparator+00 not present in FormatCode formatindex=45.
Warning: formatindex=4,44,45 are the only FormatCode elements checked for 
separator usage, there may be others that have errors.


Ok.. here's what I did:
* Changed
  * DateSeparator to '/' without trailing space.
  * ThousandSeparator to ',' without trailing space.
  * DecimalSeparator to '.' without trailing space.
  * TimeSeparator to ':' without trailing space.
  * Time100SecSeparator to '.' (same as DecimalSeparator) without trailing
space.
  * These are the separators also actually used in the format codes.
* Changed the currency formats using parentheses
  FormatCode[CURRENCY]#,##0.00;([CURRENCY]#,##0.00)/FormatCode
  to ones using minus sign instead
  FormatCode[CURRENCY]#,##0.00;-[CURRENCY]#,##0.00/FormatCode
* Changed
  * LongDateDayOfWeekSeparator from '/ ' to ', ' as that is what is used in
the date format codes.
  * LongDateDaySeparator from '/ ' to ', ' as that is what is used in
the date format codes.
  * LongDateMonthSeparator from '/ ' to ' ' as that is what is used in
the date format codes.
  * LongDateYearSeparator from '/ ' to ' ' for consistency.
* Changed
FormatElement msgid=DateFormatskey12 default=false type=short 
usage=DATE formatindex=31
  FormatCodeMM/DD/FormatCode
  to
  FormatCodeDD/MM/FormatCode
  as that was the only format in M/D order, all others are in D/M/Y order.
* Finally removed _US country designator as the data does not describe US
  conventions. As a constructed language Lojban is treated similar to
  Esperanto and Interlingua, without an assigned default country.


In cws locales34:

changeset 44511c64081e

[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-29 Thread ambershadow
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483





--- Additional comments from ambersha...@openoffice.org Sat Jan 29 23:59:10 
+ 2011 ---
Thank you. Sorry about all the problems.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-18 Thread erack
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483





--- Additional comments from er...@openoffice.org Tue Jan 18 21:45:51 + 
2011 ---
Strange language... and IMHO not well thought out, how should date from time be
distinguished if the separators are identical, in case that digits are in valid
ranges of both? And is a number like 1.23 really to be written as 1pi 23? 

Anyway, as the separator words would render most functionality using those
separators useless, the only possibility would be to have locale data with more
sane separators.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-18 Thread ambershadow
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483





--- Additional comments from ambersha...@openoffice.org Tue Jan 18 22:26:41 
+ 2011 ---
Created an attachment (id=75586)
New JBO Locale Data File


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-17 Thread er
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483


User er changed the following:

What|Old value |New value

 Assigned to|er|erack

  Ever confirmed|  |1

  Status|UNCONFIRMED   |NEW

Platform|Unknown   |All





--- Additional comments from e...@openoffice.org Mon Jan 17 10:20:47 + 
2011 ---
Reassigning to spare time account.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-17 Thread erack
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483


User erack changed the following:

What|Old value |New value

  CC|''|'erack'

 Assigned to|erack |ambershadow

  Issue type|PATCH |TASK





--- Additional comments from er...@openoffice.org Mon Jan 17 19:36:55 + 
2011 ---
Thanks, but... when test compiling I got

Warning: more than 1 character (5) in DateSeparator pi'e  not supported by
application.
Warning: more than 1 character (5) in ThousandSeparator ki'o  not supported by
application.
Warning: more than 1 character (3) in DecimalSeparator pi  not supported by
application.
Warning: more than 1 character (5) in TimeSeparator pi'e  not supported by
application.
Warning: more than 1 character (5) in Time100SecSeparator pi'e  not supported by
application.
Warning: more than 1 character (2) in ListSeparator .i not supported by 
application.
Error: DateSeparator equals TimeSeparator.
Error: ListSeparator not ';' semicolon. Strongly recommended. Currently 
required.
Warning: Time100SecSeparator equals TimeSeparator, this is probably an error.
Warning: Time100SecSeparator is different from DecimalSeparator, this may be
correct or not. Intended?
Warning: Don't forget to adapt corresponding FormatCode elements when changing
separators.
Warning: more than 1 character (2) in QuotationStart lu not supported by
application.
Warning: more than 1 character (4) in QuotationEnd li'u not supported by
application.
Warning: more than 1 character (2) in DoubleQuotationStart lu not supported by
application.
Warning: more than 1 character (4) in DoubleQuotationEnd li'u not supported by
application.
Warning: QuotationStart and QuotationEnd are both ASCII characters. Not
necessarily an error, but unusual.
Warning: DoubleQuotationStart and DoubleQuotationEnd are both ASCII characters.
Not necessarily an error, but unusual.
Warning: QuotationStart equals DoubleQuotationStart. Not necessarily an error,
but unusual.
Warning: QuotationEnd equals DoubleQuotationEnd. Not necessarily an error, but
unusual.
Warning: QuotationStart may be wrong: U+006C lu
Warning: QuotationEnd may be wrong: U+006C li'u
Warning: DoubleQuotationStart may be wrong: U+006C lu
Warning: DoubleQuotationEnd may be wrong: U+006C li'u
Error: DecimalSeparator not present in FormatCode formatindex=4.
Error: ThousandSeparator not present in FormatCode formatindex=4.
Warning: formatindex=4,44,45 are the only FormatCode elements checked for
separator usage, there may be others that have errors.
Warning: FormatCode formatindex=12 for currency uses parentheses for negative
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=13 for currency uses parentheses for negative
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=14 for currency uses parentheses for negative
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=15 for currency uses parentheses for negative
amounts, which probably is not correct for locales not based on en_US.
Warning: FormatCode formatindex=17 for currency uses parentheses for negative
amounts, which probably is not correct for locales not based on en_US.
Error: TimeSeparator not present in FormatCode formatindex=44.
Error: Time100SecSeparator not present in FormatCode formatindex=44.
Error: Time100SecSeparator+00 not present in FormatCode formatindex=44.
Warning: formatindex=4,44,45 are the only FormatCode elements checked for
separator usage, there may be others that have errors.
Error: TimeSeparator not present in FormatCode formatindex=45.
Error: Time100SecSeparator not present in FormatCode formatindex=45.
Error: Time100SecSeparator+00 not present in FormatCode formatindex=45.
Warning: formatindex=4,44,45 are the only FormatCode elements checked for
separator usage, there may be others that have errors.

At least the words as separators and quotation marks instead of characters need
to be fixed. Please see http://www.it46.se/localegen/docs/index.php and
http://hg.services.openoffice.org/DEV300/file/tip/i18npool/source/localedata/data/locale.dtd
for documentation. For further help contact the d...@l10n.openoffice.org mailing
list.

Please reassign this issue to me again once you attached corrected data.

Thanks
  Eike


-
Please do not reply to this automatically generated notification 

[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-17 Thread ambershadow
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483





--- Additional comments from ambersha...@openoffice.org Mon Jan 17 20:54:12 
+ 2011 ---
I'm not sure exactly what to do then. Because the language in question uses 
words, 
not symbols, to represent separators. So I could provide a file with default 
separators, but it would be incorrect.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-16 Thread ambershadow
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483





--- Additional comments from ambersha...@openoffice.org Mon Jan 17 01:59:40 
+ 2011 ---
Created an attachment (id=75575)
XML Lojban(JBO) locale file


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org



[l10n-issues] [Issue 116483] Lojban(JBO) Locale data file

2011-01-16 Thread ambershadow
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=116483
 Issue #|116483
 Summary|Lojban(JBO) Locale data file
   Component|l10n
 Version|current
Platform|Unknown
 URL|
  OS/Version|All
  Status|UNCONFIRMED
   Status whiteboard|
Keywords|
  Resolution|
  Issue type|PATCH
Priority|P3
Subcomponent|localedata
 Assigned to|er
 Reported by|ambershadow





--- Additional comments from ambersha...@openoffice.org Mon Jan 17 01:58:54 
+ 2011 ---
XML locale data file for Lojban(JBO) language.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: issues-unsubscr...@l10n.openoffice.org
For additional commands, e-mail: issues-h...@l10n.openoffice.org


-
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org