A weird idea (Joomla 1.6+),
wouldn't it be possible to use JText::_($mystring) or a derivate and then use the Joomla language overrides for the translations?
The user then only has to know how to add an override for his string
> On Tue, Jul 24, 2012 at 7:43 AM, parvus <par...@operamail.com> wrote:
>> Yes, indeed.
>> On Tue, 24 Jul 2012 16:41:23 +0200, Imanol P rez Iriarte
>> <eltigrequehaye...@gmail.com> wrote:
>>> Sorry, I'm coding and I misread your last post. You mean that the admin
>>> could enter any custom string with some tokens and that those custom
>>> string
>>> must be translated to many languages isn't it?
>>>> And it is then up to the user to edit the correct language.ini files? It
>>>> is not customary to provide some aid or guidance in facilitating this
>>>> job?
>>>> On Tue, 24 Jul 2012 15:11:48 +0200, Imanol P rez Iriarte <
>>>> eltigrequehaye...@gmail.com> wrote:
>>>> That's as easy as printing the strings throughout JText and defining the
>>>>> strings in as many language.ini files as languages you support.
>>>>> Take a look to the JText class: http://docs.joomla.org/JText
>>>>>> I'm the author of 'read less text'. Among others, an admin can enter a
>>>>>> custom read more text, together with {tokens} that get replaced for
>>>>>> each
>>>>>> article, so you can have a read more link that says e.g. "Read more
>>>>>> (345
>>>>>> words)".
>>>>>> I have received a request from someone who wants to use my content
>>>>>> plugin
>>>>>> (hurray!) on his multi-lingual site. So he wants to be able to have
>>>>>> these
>>>>>> fancy read more strings, which will differ per language that the site
>>>>>> offers.
>>>>>> How could I implement this request?
>>>>>> Greetings,
>>>>>> parvus
>>>>>> On Tue, 24 Jul 2012 09:03:27 +0200, Ove <tobby.eriks...@gmail.com>
>>>>>> wrote:
>>>>>> Hi parvus,
>>>>>>> you may have to be more precise when you ask about multi language.
>>>>>>> There
>>>>>>> are at least 3 "levels".
>>>>>>> (Below please read content as content and not as article)
>>>>>>> 1. To use Joomla in another language as english. Use translated
>>>>>>> language
>>>>>>> packs as Nick linked to
>>>>>>> 2. A site presented in more then 1 language with more or less
>>>>>>> independent
>>>>>>> content. This is supported by the Joomla 2.5 core extensions.
>>>>>>> Implementation steps can be found e.g. http://docs.joomla.org/** >>>>>>> Language_Switcher_Tutorial_****for_Joomla_1.6<http://docs.**
>>>>>>> 3. A site with translated content.where the translated content are
>>>>>>> related to each other. Not supported by Joomla 2.5. I've seen an
>>>>>>> extension
>>>>>>> in the JED that supports tracking of content-article translations.
>>>>>>> JoomFish
>>>>>>> was the solution for Joomla 1.5. I didn't check if it's now available
>>>>>>> for
>>>>>>> Joomla 2.5 but I know it was planned for release.
>>>>>>> All levels of multi language are very much an issue for Joomla
>>>>>>> developers. If you develop an extension it should at least meat up
>>>>>>> with
>>>>>>> "level 2".
>>>>>>> regards
>>>>>>> ove
>>>>>>> parvus skrev 23.07.2012 22:54:
>>>>>>> How can I add multi-lingual support for a content plugin?
>>>>>>>> but I was hoping someone could provide me with more (and better)
>>>>>>>> pointers.
>>>>>>>> Thanks.
>>>>>>>> --
>>>>>> You received this message because you are subscribed to the Google
>>>>>> Groups
>>>>>> "Joomla! General Development" group.
>>>>>> To post to this group, send an email to joomla-dev-general@**
>>>>>> googlegroups.com
>>>>>> <joomla-dev-general@**googlegroups.com<joomla-dev-general@googlegroups.com>
>>>>>>> .
>>>>>> To unsubscribe from this group, send email to joomla-dev-general+**
>>>>>> unsubscribe@googlegroups.com<j**oomla-dev-general%**
>>>> --
>>>> You received this message because you are subscribed to the Google Groups
>>>> "Joomla! General Development" group.
>>>> To post to this group, send an email to joomla-dev-general@**
>>>> googlegroups.com <joomla-dev-general@googlegroups.com>.
>>>> To unsubscribe from this group, send email to joomla-dev-general+**
>>>> unsubscribe@googlegroups.com<joomla-dev-general%2Bunsubscribe@googlegroups. com>
>>>> .
>>>> For more options, visit this group at http://groups.google.com/**
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! General Development" group.
>> To post to this group, send an email to joomla-dev-general@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-general+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-general?hl=en-GB.
I'd like to see this added to the Joomla core as an option for developers
to use, so please submit it as a feature for Joomla 3.0 if you decide to
use it. That will save you from having to maintain the code for all your
extensions and will also add a very worth-while contribution to the Joomla
Community.
>> Sorry, I'm coding and I misread your last post. You mean that the admin
>> could enter any custom string with some tokens and that those custom
>> string
>> must be translated to many languages isn't it?
>>> And it is then up to the user to edit the correct language.ini files?
>>> It
>>> is not customary to provide some aid or guidance in facilitating this
>>> job?
>>> That's as easy as printing the strings throughout JText and defining
>>> the
>>>> strings in as many language.ini files as languages you support.
>>>> Take a look to the JText class: http://docs.joomla.org/JText
>>>>> I'm the author of 'read less text'. Among others, an admin can enter
>>>>> a
>>>>> custom read more text, together with {tokens} that get replaced for
>>>>> each
>>>>> article, so you can have a read more link that says e.g. "Read more
>>>>> (345
>>>>> words)".
>>>>> I have received a request from someone who wants to use my content
>>>>> plugin
>>>>> (hurray!) on his multi-lingual site. So he wants to be able to have
>>>>> these
>>>>> fancy read more strings, which will differ per language that the site
>>>>> offers.
>>>>> How could I implement this request?
>>>>> Greetings,
>>>>> parvus
>>>>> On Tue, 24 Jul 2012 09:03:27 +0200, Ove <tobby.eriks...@gmail.com>
>>>>> wrote:
>>>>> Hi parvus,
>>>>>> you may have to be more precise when you ask about multi language.
>>>>>> There
>>>>>> are at least 3 "levels".
>>>>>> (Below please read content as content and not as article)
>>>>>> 1. To use Joomla in another language as english. Use translated
>>>>>> language
>>>>>> packs as Nick linked to
>>>>>> 2. A site presented in more then 1 language with more or less
>>>>>> independent
>>>>>> content. This is supported by the Joomla 2.5 core extensions.
>>>>>> Implementation steps can be found e.g. http://docs.joomla.org/** >>>>>> Language_Switcher_Tutorial_****for_Joomla_1.6<http://docs.** >>>>>> joomla.org/Language_Switcher_**Tutorial_for_Joomla_1.6<http://docs.joomla.org/Language_Switcher_Tutorial_for_Joomla_1.6>
>>>>>> 3. A site with translated content.where the translated content are
>>>>>> related to each other. Not supported by Joomla 2.5. I've seen an
>>>>>> extension
>>>>>> in the JED that supports tracking of content-article translations.
>>>>>> JoomFish
>>>>>> was the solution for Joomla 1.5. I didn't check if it's now
>>>>>> available
>>>>>> for
>>>>>> Joomla 2.5 but I know it was planned for release.
>>>>>> All levels of multi language are very much an issue for Joomla
>>>>>> developers. If you develop an extension it should at least meat up
>>>>>> with
>>>>>> "level 2".
>>>>>> regards
>>>>>> ove
>>>>>> parvus skrev 23.07.2012 22:54:
>>>>>> How can I add multi-lingual support for a content plugin?
>>>>>>> --
>>>>> You received this message because you are subscribed to the Google
>>>>> Groups
>>>>> "Joomla! General Development" group.
>>>>> To post to this group, send an email to joomla-dev-general@**
>>>>> googlegroups.com
>>>>> <joomla-dev-general@**googlegroups.com<joomla-dev-general@googlegroups.com>
>>>>> >.
>>>>> To unsubscribe from this group, send email to joomla-dev-general+**
>>>>> unsubscribe@googlegroups.com<j**oomla-dev-general%**
>>>>> 2Bunsubscribe@googlegroups.com<joomla-dev-general%252Bunsubscribe@googlegro ups.com>
>>>>> **>
>>>>> .
>>>>> For more options, visit this group at http://groups.google.com/** >>>>> group/joomla-dev-general?hl=****en-GB<http://groups.google.** >>>>> com/group/joomla-dev-general?**hl=en-GB<http://groups.google.com/group/joomla-dev-general?hl=en-GB>
>>>>> .
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups
>>> "Joomla! General Development" group.
>>> To post to this group, send an email to joomla-dev-general@**
>>> googlegroups.com <joomla-dev-general@googlegroups.com>.
>>> To unsubscribe from this group, send email to joomla-dev-general+**
>>> unsubscribe@googlegroups.com<joomla-dev-general%2Bunsubscribe@googlegroups. com>
>>> .
>>> For more options, visit this group at http://groups.google.com/** >>> group/joomla-dev-general?hl=**en-GB<http://groups.google.com/group/joomla-dev-general?hl=en-GB>
>>> .
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! General Development" group.
> To post to this group, send an email to
> joomla-dev-general@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-general+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-general?hl=en-GB.
I wasn't going to post in this thread but since it won't die. ..
If you read the GPL and particularly GPL3 it says that "appropriate legal notices" may not be removed or added without the permission of the original copyright holder. The Joomla project displays the GPL as part of the installation procedure for the Joomla CMS. That means You may not remove that display even if you fork Joomla and distribute it as a GPL application under your own name unless you get specific permission to do so from OSM. You also may not add new notices without specific permission to do so and you may not mandate that others include such notices. The Joomla project has always taken the position that after installation the GPL information only has to be retained in the source code of each individual file, not visibly in the application and therefore no matter what an extension developer does those are the rules that apply unless a specific exception is granted.
On Tuesday, July 24, 2012 9:31:05 AM UTC-4, Thomas PAPIN wrote:
> (found on some forum about phpbb notice)
> In the GPL v2
> *1) "Activities other than copying, distribution and modification are not > covered by this License; they are outside its scope. The act of running > the Program is not restricted, and the output from the Program is covered > only if its contents constitute a work based on the Program (independent of > having been made by running the Program). Whether that is true depends on > what the Program does. "*
> So seems that only the copyright in the source code is impacted. the > notice in the "output from the program" is not covered.
> *2) "that you conspicuously and appropriately publish on each copy an > appropriate copyright notice and disclaimer of warranty; keep intact all > the notices that refer to this License and to the absence of any > warranty; and give any other recipients of the Program a copy of this > License along with the Program."
> *
> Seems that only the notices that refer to the license should be keep > intact. > No refer to the GPL license => can be removed ? so footer notice could be > removed ?
> 3) They was a long long long thread about "is it possible to have a non > GPL extension for Joomla, as the component is using function of the GPL > framework ?". This question was not answered or every one has a different > point of view (because of how php is working, no link,etc..). This is still > a open question in the php world (not just Joomla).
> I am curious to know if someone already try to request the source code to > someone selling joomla component software under a non GPL license with > crypt code. Saying your software is using GPL code, so your license is GPL > too. And if someone went to the tribunal to get the source.
>> Le mardi 24 juillet 2012 13:05:29 UTC+2, Valandis a écrit :
>>> Hi Nick. I meant the topic of this thread is "Joomla GPL Extensions and >>> Removal of Backlinks" and Parvus' question about Multi-lingual support >>> for extensions has nothing to do with that.
>>> On Tuesday, 24 July 2012 05:39:19 UTC+2, Nick Savov wrote:
>>>> Actually, language packs for extensions is definitely on-topic.
>>>> Kind regards, >>>> Nick
>>>> > It seems you posted in the wrong thread Parvus. Your post is >>>> off-topic.
>>>> > On Monday, 23 July 2012 22:54:22 UTC+2, parvus wrote:
>>>> >> How can I add multi-lingual support for a content plugin?
>> To post to this group, send an email to >> joomla-dev-general@googlegroups.com.
>> To unsubscribe from this group, send email to >> joomla-dev-general+unsubscribe@googlegroups.com.
>> For more options, visit this group at >> http://groups.google.com/group/joomla-dev-general?hl=en-GB.
In this specific case, we get into an issue with plurals depending on languages.
I.e. as you should use
JText::plural('MY_CONSTANT_WHATEVER', $myvariable)
The strings constants may differ depending on languages.
will need 4 constants with different suffixes
COM_BANNERS_BANNERS_N_ITEMS_CHECKED_IN_0
COM_BANNERS_BANNERS_N_ITEMS_CHECKED_IN_1
COM_BANNERS_BANNERS_N_ITEMS_CHECKED_IN_2
COM_BANNERS_BANNERS_N_ITEMS_CHECKED_IN_FEW
>Sorry, I'm coding and I misread your last post. >You mean that the admin could enter any custom >string with some tokens and that those custom >string must be translated to many languages >isn't it?
>And it is then up to the user to edit the >correct language.ini files? It is not customary >to provide some aid or guidance in facilitating >this job?
>That's as easy as printing the strings throughout JText and defining the
>strings in as many language.ini files as languages you support.
>Take a look to the JText class: ><http://docs.joomla.org/JText>http://docs.joomla.org/JText
>I'm the author of 'read less text'. Among others, an admin can enter a
>custom read more text, together with {tokens} that get replaced for each
>article, so you can have a read more link that says e.g. "Read more (345
>words)".
>I have received a request from someone who wants to use my content plugin
>(hurray!) on his multi-lingual site. So he wants to be able to have these
>fancy read more strings, which will differ per language that the site
>offers.
>How could I implement this request?
>Greetings,
>parvus
>On Tue, 24 Jul 2012 09:03:27 +0200, Ove ><<mailto:tobby.eriks...@gmail.com>tobby.eriks...@gmail.com> >wrote:
> Hi parvus,
>you may have to be more precise when you ask about multi language. There
>are at least 3 "levels".
>(Below please read content as content and not as article)
>1. To use Joomla in another language as english. Use translated language
>packs as Nick linked to
>2. A site presented in more then 1 language with more or less independent
>content. This is supported by the Joomla 2.5 core extensions.
>3. A site with translated content.where the translated content are
>related to each other. Not supported by Joomla 2.5. I've seen an extension
>in the JED that supports tracking of content-article translations. JoomFish
>was the solution for Joomla 1.5. I didn't check if it's now available for
>Joomla 2.5 but I know it was planned for release.
>All levels of multi language are very much an issue for Joomla
>developers. If you develop an extension it should at least meat up with
>"level 2".
>regards
>ove
>parvus skrev 23.07.2012 22:54:
>How can I add multi-lingual support for a content plugin?
>--
>You received this message because you are >subscribed to the Google Groups "Joomla! General >Development" group.
>To post to this group, send an email to ><mailto:joomla-dev-general@googlegroups.com>joomla-dev-general@googlegroup s.com.
>To unsubscribe from this group, send email to ><mailto:joomla-dev-general%2Bunsubscribe@googlegroups.com>joomla-dev-gener al+unsubscribe@googlegroups.com.
>For more options, visit this group at ><http://groups.google.com/group/joomla-dev-general?hl=en-GB>http://groups.google.com/group/joomla-dev-general?hl=en-GB.
>--
>You received this message because you are >subscribed to the Google Groups "Joomla! General >Development" group.
>To post to this group, send an email to joomla-dev-general@googlegroups.com.
>To unsubscribe from this group, send email to >joomla-dev-general+unsubscribe@googlegroups.com.
>For more options, visit this group at >http://groups.google.com/group/joomla-dev-general?hl=en-GB.
--
>Please keep the Subject wording in your answers
This e-mail and any attachments may be confidential. You must not disclose or use the information contained in this e-mail if you are not the
intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies.
-----------------------------------------------------------
Jean-Marie Simonet / infograf768
Joomla Production Working group
Joomla! Translation Coordination Team
@parvus, Imanol, Sam Moffat and Jean-Marie: this thread is about GPL and backlink removal. Please create a new thread for your discussion about multilingual support for extensions here. Thanks.
@Thomas Papin: please read the complete GPL license. Forbidding removal of copyright notices in the output of the program, as mentionned previously by Elin and Myself is done in paragraph 2.c of GPL version 2 and paragraph 5.d of GPL version 3.
Simply put: you cannot remove a copyright notice if there is already one, unless you have agreement from previous copyright owner(s) - with an s: if there are several copyright owners, you need approval from those owners you want to remove the copyright notice in the program visible output.
Contrary to Elin however, I don't read in that paragraph that you are not allowed to add your own notices. The actual text in version 2 is:
*c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) *
@Jm Yes, this is indeed a concern, especially since sprintf is used, and
not something like '{0}'.format() from Python or String.Format from C# or
..
For me personally, Ove's suggestion looks very simple, and suitable for my
content plugin (it already contains enough code as it is now...). I think
I'll follow that path.
“Additional permissions” are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permissions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supplement the terms of this License with terms:
- a) Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License; or
- b) Requiring preservation of specified reasonable legal notices or author attributions in that material or in the Appropriate Legal Notices displayed by works containing it; or
- c) Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such material be marked in reasonable ways as different from the original version; or
- d) Limiting the use for publicity purposes of names of licensors or authors of the material; or
- e) Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
- f) Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered “further restrictions” within the meaning of section 10. If the Program as you received it, or any part of it, contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document, provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files, or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either way.
+1 for the creation of another thread regarding "multilingual support for extensions". I tried to explain to parvus and Nick Savov before, but they misunderstood me I suppose.
As it regards the topic I started a while ago, I see there isn't a solid answer to my first question. I see people understand the GPL differently than others. I myself, see it as Elin does and Thomas does. I believe only copyright notices that are found inside the source should be kept intact, but not visible ones.
Read what Matt Lipscomb posted up there and I find it absolutely correct:
> 2) All backlinks may be removed from an extension - that's the point of > opensource software - you can modify it however you like. The copyright > notice from the developer in the *source code* must be left in tact - but > otherwise - do as you wish with it.
On Wednesday, July 25, 2012 6:28:21 PM UTC+2, shumisha wrote:
> Hi
> @parvus, Imanol, Sam Moffat and Jean-Marie: this thread is about GPL and > backlink removal. Please create a new thread for your discussion about > multilingual support for extensions here. Thanks.
> @Thomas Papin: please read the complete GPL license. Forbidding removal of > copyright notices in the output of the program, as mentionned previously by > Elin and Myself is done in paragraph 2.c of GPL version 2 and paragraph 5.d > of GPL version 3.
> Simply put: you cannot remove a copyright notice if there is already one, > unless you have agreement from previous copyright owner(s) - with an s: if > there are several copyright owners, you need approval from those owners you > want to remove the copyright notice in the program visible output.
> Contrary to Elin however, I don't read in that paragraph that you are not > allowed to add your own notices. The actual text in version 2 is:
> *c) If the modified program normally reads commands interactively when > run, you must cause it, when started running for such interactive use in > the most ordinary way, to print or display an announcement including an > appropriate copyright notice and a notice that there is no warranty (or > else, saying that you provide a warranty) and that users may redistribute > the program under these conditions, and telling the user how to view a copy > of this License. (Exception: if the Program itself is interactive but does > not normally print such an announcement, your work based on the Program is > not required to print an announcement.) *
I will try contact them directly to make this hijacking stop.
@Elin, thanks. I don't see how the text you quoted prevent you from adding your own notices. Actually, it doesn't change the terms of GPL 2 or 3 which *forces* you to add visible copyright notices, and only talk about a few additional restrictions you are allowed to add to the license terms, plus the fact that you can remove any "restricting" terms that a previous contributor may have added. Anyway, I think better leave this topic off for now, as this thread is already extremely and unfortunately very confusing.
@valandis: I think the answer is pretty solid, if one just read the license either in version 2 or 3. What Matt Lipscomb says in the paragraph you quoted is not correct. Paragraph 2.c og GPL version 2 says:
*c) If the modified program normally reads commands interactively when run, you must cause it, when started running for such interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.) *
This paragraph explicitely prevent anyone from removing a copyright notice in the *visible output* of a GPL-licensed program. The well-known "keep the source code copyright notice but do as you wish with the rest of the code" is just a common-language approximation, but the license does put a (at least one) restriction on what you can do with the source code, and that is you cannot cause the removal of visible copyright notice if there are any.
As previously stated, GPL version 3 has the same provision in paragraph 5.d.
Rgds
Le jeudi 26 juillet 2012 08:50:42 UTC+2, Valandis a écrit :
> +1 for the creation of another thread regarding "multilingual support for > extensions". I tried to explain to parvus and Nick Savov before, but they > misunderstood me I suppose.
> As it regards the topic I started a while ago, I see there isn't a solid > answer to my first question. I see people understand the GPL differently > than others. I myself, see it as Elin does and Thomas does. I believe only > copyright notices that are found inside the source should be kept intact, > but not visible ones.
> Read what Matt Lipscomb posted up there and I find it absolutely correct:
>> 2) All backlinks may be removed from an extension - that's the point of >> opensource software - you can modify it however you like. The copyright >> notice from the developer in the *source code* must be left in tact - but >> otherwise - do as you wish with it.
> Best
> On Wednesday, July 25, 2012 6:28:21 PM UTC+2, shumisha wrote:
>> Hi
>> @parvus, Imanol, Sam Moffat and Jean-Marie: this thread is about GPL and >> backlink removal. Please create a new thread for your discussion about >> multilingual support for extensions here. Thanks.
>> @Thomas Papin: please read the complete GPL license. Forbidding removal >> of copyright notices in the output of the program, as mentionned previously >> by Elin and Myself is done in paragraph 2.c of GPL version 2 and paragraph >> 5.d of GPL version 3.
>> Simply put: you cannot remove a copyright notice if there is already one, >> unless you have agreement from previous copyright owner(s) - with an s: if >> there are several copyright owners, you need approval from those owners you >> want to remove the copyright notice in the program visible output.
>> Contrary to Elin however, I don't read in that paragraph that you are not >> allowed to add your own notices. The actual text in version 2 is:
>> *c) If the modified program normally reads commands interactively when >> run, you must cause it, when started running for such interactive use in >> the most ordinary way, to print or display an announcement including an >> appropriate copyright notice and a notice that there is no warranty (or >> else, saying that you provide a warranty) and that users may redistribute >> the program under these conditions, and telling the user how to view a copy >> of this License. (Exception: if the Program itself is interactive but does >> not normally print such an announcement, your work based on the Program is >> not required to print an announcement.) *
I check these within my email client and the subject is simply "[jgen]
Multi-lingual support for extensions", so it's hard to know whether
someone else has created a new topic or added onto another one and changed
the subject.
> +1 for the creation of another thread regarding "multilingual support for
> extensions". I tried to explain to parvus and Nick Savov before, but they
> misunderstood me I suppose.
> As it regards the topic I started a while ago, I see there isn't a solid
> answer to my first question. I see people understand the GPL differently
> than others. I myself, see it as Elin does and Thomas does. I believe only
> copyright notices that are found inside the source should be kept intact,
> but not visible ones.
> Read what Matt Lipscomb posted up there and I find it absolutely correct:
>> 2) All backlinks may be removed from an extension - that's the point of
>> opensource software - you can modify it however you like. The copyright
>> notice from the developer in the *source code* must be left in tact -
>> but
>> otherwise - do as you wish with it.
> Best
> On Wednesday, July 25, 2012 6:28:21 PM UTC+2, shumisha wrote:
>> Hi
>> @parvus, Imanol, Sam Moffat and Jean-Marie: this thread is about GPL and
>> backlink removal. Please create a new thread for your discussion about
>> multilingual support for extensions here. Thanks.
>> @Thomas Papin: please read the complete GPL license. Forbidding removal
>> of
>> copyright notices in the output of the program, as mentionned previously
>> by
>> Elin and Myself is done in paragraph 2.c of GPL version 2 and paragraph
>> 5.d
>> of GPL version 3.
>> Simply put: you cannot remove a copyright notice if there is already
>> one,
>> unless you have agreement from previous copyright owner(s) - with an s:
>> if
>> there are several copyright owners, you need approval from those owners
>> you
>> want to remove the copyright notice in the program visible output.
>> Contrary to Elin however, I don't read in that paragraph that you are
>> not
>> allowed to add your own notices. The actual text in version 2 is:
>> *c) If the modified program normally reads commands interactively when
>> run, you must cause it, when started running for such interactive use in
>> the most ordinary way, to print or display an announcement including an
>> appropriate copyright notice and a notice that there is no warranty (or
>> else, saying that you provide a warranty) and that users may
>> redistribute
>> the program under these conditions, and telling the user how to view a
>> copy
>> of this License. (Exception: if the Program itself is interactive but
>> does
>> not normally print such an announcement, your work based on the Program
>> is
>> not required to print an announcement.) *
>> Rgds
> --
> You received this message because you are subscribed to the Google Groups
> "Joomla! General Development" group.
> To view this discussion on the web, visit
> https://groups.google.com/d/msg/joomla-dev-general/-/rfbTwVpPJm8J.
> To post to this group, send an email to
> joomla-dev-general@googlegroups.com.
> To unsubscribe from this group, send email to
> joomla-dev-general+unsubscribe@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/joomla-dev-general?hl=en-GB.
With any luck Google Groups will update their threading to be inline
with GMail's ability to detect when someone rewrites the entire email
and intelligently start a new thread. Unfortunately Google Groups
seems to be the abandoned child and they're only interested in badly
updating the UI to make it less usable and more frustrating. Long live
deja news.
On Fri, Jul 27, 2012 at 9:51 AM, Nick Savov <n...@iowawebcompany.com> wrote:
> I understood you after your clarification.
> I check these within my email client and the subject is simply "[jgen]
> Multi-lingual support for extensions", so it's hard to know whether
> someone else has created a new topic or added onto another one and changed
> the subject.
> Kind regards,
> Nick
>> +1 for the creation of another thread regarding "multilingual support for
>> extensions". I tried to explain to parvus and Nick Savov before, but they
>> misunderstood me I suppose.
>> As it regards the topic I started a while ago, I see there isn't a solid
>> answer to my first question. I see people understand the GPL differently
>> than others. I myself, see it as Elin does and Thomas does. I believe only
>> copyright notices that are found inside the source should be kept intact,
>> but not visible ones.
>> Read what Matt Lipscomb posted up there and I find it absolutely correct:
>>> 2) All backlinks may be removed from an extension - that's the point of
>>> opensource software - you can modify it however you like. The copyright
>>> notice from the developer in the *source code* must be left in tact -
>>> but
>>> otherwise - do as you wish with it.
>> Best
>> On Wednesday, July 25, 2012 6:28:21 PM UTC+2, shumisha wrote:
>>> Hi
>>> @parvus, Imanol, Sam Moffat and Jean-Marie: this thread is about GPL and
>>> backlink removal. Please create a new thread for your discussion about
>>> multilingual support for extensions here. Thanks.
>>> @Thomas Papin: please read the complete GPL license. Forbidding removal
>>> of
>>> copyright notices in the output of the program, as mentionned previously
>>> by
>>> Elin and Myself is done in paragraph 2.c of GPL version 2 and paragraph
>>> 5.d
>>> of GPL version 3.
>>> Simply put: you cannot remove a copyright notice if there is already
>>> one,
>>> unless you have agreement from previous copyright owner(s) - with an s:
>>> if
>>> there are several copyright owners, you need approval from those owners
>>> you
>>> want to remove the copyright notice in the program visible output.
>>> Contrary to Elin however, I don't read in that paragraph that you are
>>> not
>>> allowed to add your own notices. The actual text in version 2 is:
>>> *c) If the modified program normally reads commands interactively when
>>> run, you must cause it, when started running for such interactive use in
>>> the most ordinary way, to print or display an announcement including an
>>> appropriate copyright notice and a notice that there is no warranty (or
>>> else, saying that you provide a warranty) and that users may
>>> redistribute
>>> the program under these conditions, and telling the user how to view a
>>> copy
>>> of this License. (Exception: if the Program itself is interactive but
>>> does
>>> not normally print such an announcement, your work based on the Program
>>> is
>>> not required to print an announcement.) *
>>> Rgds
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Joomla! General Development" group.
>> To view this discussion on the web, visit
>> https://groups.google.com/d/msg/joomla-dev-general/-/rfbTwVpPJm8J.
>> To post to this group, send an email to
>> joomla-dev-general@googlegroups.com.
>> To unsubscribe from this group, send email to
>> joomla-dev-general+unsubscribe@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/joomla-dev-general?hl=en-GB.
> --
> You received this message because you are subscribed to the Google Groups "Joomla! General Development" group.
> To post to this group, send an email to joomla-dev-general@googlegroups.com.
> To unsubscribe from this group, send email to joomla-dev-general+unsubscribe@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/joomla-dev-general?hl=en-GB.