> I am not sure the proper way to do this, and I hope someone can assist
> me formalizing and sending this patch to the patches list, or to a
> maintainer directly --
Since Koha relies already on YUI, why not switching from TinyMCE to YUI
text editor?
http://developer.yahoo.com/yui/editor/
-
All,
I am not sure the proper way to do this, and I hope someone can assist me
formalizing and sending this patch to the patches list, or to a maintainer
directly --
TinyMCE is only (as far as I can tell) being used for the help editor. This
is a 3mb package that is copied to every language spec
On Tue, Dec 30, 2008 at 12:37 PM, Chris Cormack
wrote:
> On Tue, Dec 30, 2008 at 12:34 PM, Stan Brinkerhoff
> wrote:
>> The javascript directories seem to gobble a ton of space -- perhaps moving
>> all of the Javascript libraries into a 'common' directory outside of the
>> language specific temp
On Tue, Dec 30, 2008 at 12:34 PM, Stan Brinkerhoff wrote:
> The javascript directories seem to gobble a ton of space -- perhaps moving
> all of the Javascript libraries into a 'common' directory outside of the
> language specific templates could be done. In my quick test that saved
> ~200mb of di
The javascript directories seem to gobble a ton of space -- perhaps moving
all of the Javascript libraries into a 'common' directory outside of the
language specific templates could be done. In my quick test that saved
~200mb of disk space, and brought the compressed distribution to ~27mb (from
47
Joe Atzberger wrote:
> I'm all for consolidation where it makes the code less duplicative and
> more maintainable. But if the motivation is just to "save" 20 MB, I
> might still be for it, but not really inspired. 20 MB of disk is a lot
> cheaper than developer time.
You are speaking of compr
Hi,
On Mon, Dec 29, 2008 at 11:04 AM, Nahuel ANGELINETTI
wrote:
> Some question about COinS support in Koha, we will integrate the
> unimarc support of COinS in koha, but I have some question about it.
> Actually only "am" document type is "managed", but why? I think it's
> too much restrictive,
On Mon, Dec 29, 2008 at 11:50 AM, Stan Brinkerhoff wrote:
> All,
>
> Has there been any discussion about trimming down the size of the Koha
> distribution? The issue it seems isn't the code; but rather items such as
> TinyMCE being copied into every template directory, and the /misc/ folder is
>
All,
Has there been any discussion about trimming down the size of the Koha
distribution? The issue it seems isn't the code; but rather items such as
TinyMCE being copied into every template directory, and the /misc/ folder is
rather huge. It seems as though the 47mb tar file could easily be 20-
On Mon, Dec 29, 2008 at 9:15 AM, Ryan Higgins wrote:
> I intend to submit a patch this week that will add an include to the
> staff side: base-js.inc , which includes js that needs to be processed
> by H::T::P. It will include a global 'koha' object, which could store an
> array of strings for tr
I intend to submit a patch this week that will add an include to the
staff side: base-js.inc , which includes js that needs to be processed
by H::T::P. It will include a global 'koha' object, which could store an
array of strings for translation. If accepted, the same could be done
for the opac.
The convention is to use _(), BUT tmpl_process doesn't parse the ".js"
files. So they're not putted in po translation files and translators
cannot translate them.
Only
Hi,
Some question about COinS support in Koha, we will integrate the
unimarc support of COinS in koha, but I have some question about it.
Actually only "am" document type is "managed", but why? I think it's
too much restrictive, we should only parse the first char of record
type(in leader) and com
I think the convention has been to use the underscore function to designate
translatable string literals like:
alert( _("Error: barcode empty!") );
Whether that is actually working or not, I'll have to leave for someone else
to answer.
--Joe
On Mon, Dec 29, 2008 at 10:25 AM, Nahuel ANGELINETTI w
Hi all,
We saw the javascript files(.js) are not translated. In fact,
only .tmpl and .inc strings are exported in po files.
Some developers added some strings to be translated in javascript files
(Like "Cart" button in OPAC), so when we translate in french, there is
no translation for those string
Zeno Tajoli a écrit :
> Hi to all,
>
Hi Zeno,
> Reading the wiki page
> http://wiki.koha.org/doku.php?id=en:installation:win32:koha_3_win32_installer_project
> it think that there problems on the use of perl module XML::LibXSLT.
>
> I think it is a must for a working Koha 3.0 on windows.
> Is it
Rick Welykochy a écrit :
> Exactly where is it needed?
>
> Is it required for web page output to stdout?
>
If i'm not mistaken, HTML::Template::Pro take cares of that (it was not
the case of HTML::Template)
> Is it required when Koha creates a CSV file as output?
>
yes.
--
Paul POULAIN
htt
17 matches
Mail list logo
