Closed
Bug 295465
Opened 19 years ago
Closed 19 years ago
Add myspell to Tb source l10n
Categories
(Thunderbird :: Build Config, defect)
Thunderbird
Build Config
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: zbraniecki, Assigned: zbraniecki)
References
Details
Attachments
(1 file, 3 obsolete files)
6.51 KB,
patch
|
benjamin
:
review+
mscott
:
superreview+
benjamin
:
approval1.8b4+
|
Details | Diff | Splinter Review |
L10N teams need this and we want to give our users Tb with their spell dict.
Comment 1•19 years ago
|
||
Catalan localizations have always also included several dictionaries by default: Catalan, English (American and British), Spanish, French and Italian. This is really appreciated by users since dictionary installation is still not as 'easy' as it could be. Could new Thunderbird include these dictionaries as well (letting aside the license problem)?
Updated•19 years ago
|
Flags: blocking1.8b4+
Comment 2•19 years ago
|
||
Currently there is already code of different licenses in Mozilla CVS, as we can read in http://www.mozilla.org/MPL/license-policy.html. As I see, there are libraries from external projects such as jpeg with non-MPL/LGPL/GPL license. I think that dictionaries, since they are external projects/libraries as well, and they are used by Mozilla applications, could be managed in a similar way. If it's necessary, binary could have a warning in installation README about the specific licenses of dictionaries. That's the same with artwork, isn't?
Comment 3•19 years ago
|
||
Toni, other licenses are only allowed in our shipped products when they are compatible with the MPL/GPL/LGPL tri-license. Most of the dictionaries in question are not compatible, or are at least legally questionable (it doesn't actually make any sense to license a dictionary under a GPL/LGPL license, as it it not "code"). In any case, that has no bearing on this bug, which is about the build and installation systems necessary to get dictionaries installed regardless of the licensing issues.
Assignee | ||
Comment 5•19 years ago
|
||
gzipped patch (size was too big due to en-US.dic move)
Attachment #188474 -
Flags: superreview?(mscott)
Attachment #188474 -
Flags: review?(benjamin)
Assignee | ||
Comment 6•19 years ago
|
||
Assignee | ||
Updated•19 years ago
|
Attachment #188544 -
Flags: superreview?(mscott)
Attachment #188544 -
Flags: review?(benjamin)
Comment 7•19 years ago
|
||
Comment on attachment 188544 [details] [diff] [review] patch without en-US.dic|aff Since we are not going to require every l10n to provide a dictionary, we need to check that DICTIONARY_FILES exist before using them. This can be done with the makefile $(wildcard) command or with the "-f" test in the command.
Attachment #188544 -
Flags: superreview?(mscott)
Attachment #188544 -
Flags: review?(benjamin)
Attachment #188544 -
Flags: review-
Assignee | ||
Comment 8•19 years ago
|
||
Attachment #188474 -
Attachment is obsolete: true
Assignee | ||
Updated•19 years ago
|
Attachment #188544 -
Attachment is obsolete: true
Attachment #188548 -
Flags: review?(benjamin)
Comment 9•19 years ago
|
||
Comment on attachment 188548 [details] [diff] [review] patch v2 "ls" is not good makefile-fu: please use $(wildcard $(LOCALE_SRCDIR)/myspell/*.dic) or something equivalent In addition, we're going to need changes to mail/installer/windows/basemail-win to package the dictionaries in en-US.xpi instead of mail.xpi, and changes to mail/locales/Makefile.in to build this directory in the libs-% target to make extensions/myspell/locales and in the repackage-zip target to remove the en-US dictionaries (if that's actually the plan, which it seems to be from this patch).
Attachment #188548 -
Flags: review?(benjamin) → review-
Updated•19 years ago
|
Attachment #188474 -
Flags: superreview?(mscott)
Attachment #188474 -
Flags: review?(benjamin)
Comment 10•19 years ago
|
||
I'm pretty sure there are some nasty licensing issues with non english dictionaries that prevent us from putting them in the source tree. This has come up before IIRC.
Comment 11•19 years ago
|
||
(In reply to comment #10) > I'm pretty sure there are some nasty licensing issues with non english > dictionaries that prevent us from putting them in the source tree. This has come > up before IIRC. We (bsmedberg, gandalf, Pike and the L10n community) know about that. We can include a certain amount of dictionaries though. And before we can even think of the licensing issues, which are different for each and every dictionary out there, we have to support including them first. This is what that bug and patch aims to do. Read the end of comment #3. We'll deal with that somewhere else, once we have support for shipping them at all.
Comment 12•19 years ago
|
||
mscott, we know about these issues: this patch is only the build infrastructure so that if there are dictionaries with acceptable licenses we can use them.
Assignee | ||
Comment 13•19 years ago
|
||
wildcard used
Attachment #188548 -
Attachment is obsolete: true
Attachment #188669 -
Flags: review?(benjamin)
Comment 14•19 years ago
|
||
Comment on attachment 188669 [details] [diff] [review] patch v3 did you read this patch before attaching it? ;-) please fix topsrcdir/srcdir/VPATH to use the appropriate @macros@. And please use *.dic and *.aff instead of *.* so that we don't pick up random other files (including the CVS directory).
Attachment #188669 -
Flags: review?(benjamin) → review+
Assignee | ||
Comment 15•19 years ago
|
||
Comment on attachment 188669 [details] [diff] [review] patch v3 I fixed topsrcdir,srcdir and VPATH locally and changed DICTIONARY_FILES to grab only dic and aff files.
Attachment #188669 -
Flags: superreview?(mscott)
Updated•19 years ago
|
Attachment #188669 -
Flags: superreview?(mscott) → superreview+
Assignee | ||
Updated•19 years ago
|
Attachment #188669 -
Flags: approval1.8b4?
Updated•19 years ago
|
Attachment #188669 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 16•19 years ago
|
||
checked in
Updated•19 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Comment 17•19 years ago
|
||
Comment on attachment 188669 [details] [diff] [review] patch v3 Probably the cause of bug 301969.
You need to log in
before you can comment on or make changes to this bug.
Description
•