[jira] [Resolved] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Wright resolved CONNECTORS-385. Resolution: Fixed Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188396#comment-13188396 ] Karl Wright commented on CONNECTORS-385: r1232822 uses JAVA_TOOL_OPTIONS to set -Dfile.encoding=UTF8 for the JVMS that forrest starts. Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-380) Need a UI test for the Alfresco connector
[
https://issues.apache.org/jira/browse/CONNECTORS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188411#comment-13188411
]
Piergiorgio Lucidi commented on CONNECTORS-380:
---
added the UI test implementation for the Alfresco connector, updated javascript
and html templates (r1232839) but there are errors during the execution. I have
to investigate again...
It seems that the same error now is returned from the CMIS UI Test execution.
Alfresco UI Test
{code}
[junit] Multipart posting url
'http://localhost:8346/mcf-crawler-ui/execute.jsp' with parameters
'username=admintenantDomain=password=adminthrottlecount=0description=connname=MyRepositoryConnectionisnewconnection=trueserver=localhostclassname=org.apache.manifoldcf.crawler.connectors.alfresco.AlfrescoRepositoryConnectortabname=Namemaxconnections=10protocol=httppath=%2Falfresco%2Fapiauthorityname=_none_type=connectionport=9090op=Continue'
and 0 files...
[junit] Traceback (most recent call last):
[junit] File test.py, line 121, in module
[junit] var87.click()
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/VirtualBrowser.py,
line 120, in click
[junit] self.get_form( ).execute_javascript_expression( self.onclick )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/VirtualBrowser.py,
line 672, in execute_javascript_expression
[junit] return self.window_instance.execute_javascript_expression(
javascript )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/VirtualBrowser.py,
line 920, in execute_javascript_expression
[junit] return tokenstream.evaluate_expr( self.jscontext, HTML )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1085, in evaluate_expr
[junit] rval = self.evaluate_expr1( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1120, in evaluate_expr1
[junit] rval = self.evaluate_expr2( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1164, in evaluate_expr2
[junit] return self.evaluate_expr3( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1176, in evaluate_expr3
[junit] rval = self.evaluate_expr4( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1264, in evaluate_expr4
[junit] rval = self.evaluate_expr5( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1299, in evaluate_expr5
[junit] rval = self.evaluate_expr6( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1341, in evaluate_expr6
[junit] return self.evaluate_expr7( context, place, parse_only )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 1438, in evaluate_expr7
[junit] return reference_object.call( arguments, context )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 554, in call
[junit] return self.get_referenced_object().call(argset,context)
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 186, in call
[junit] response = ts.evaluate_statement( context, method %s %
self.name )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 752, in evaluate_statement
[junit] result = self.evaluate_statement( newscope, place )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 810, in evaluate_statement
[junit] rval = self.evaluate_statement( context, place )
[junit] File
/Users/piergiorgiolucidi/Documents/workspaces/manifold/manifold/tests/alfresco/test-derby-output/Javascript.py,
line 752, in evaluate_statement
[junit] result = self.evaluate_statement( newscope, place )
[junit] File
[jira] [Resolved] (CONNECTORS-380) Need a UI test for the Alfresco connector
[ https://issues.apache.org/jira/browse/CONNECTORS-380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Piergiorgio Lucidi resolved CONNECTORS-380. --- Resolution: Fixed r1232849. Need a UI test for the Alfresco connector - Key: CONNECTORS-380 URL: https://issues.apache.org/jira/browse/CONNECTORS-380 Project: ManifoldCF Issue Type: Test Components: Alfresco connector Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.5 The Alfresco connector needs a UI test, and needs whatever modifications are needed to its UI to make it testable. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
Subscribe request result (debian-doc ML)
Hi, I am the fml ML manager for the ML debian-...@debian.or.jp. --debian-...@debian.or.jp, Be Seeing You! If you have any questions or problems, please contact debian-doc-ad...@debian.or.jp
[jira] [Created] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
Upgrade the Crawler UI framework with Apache Velocity - Key: CONNECTORS-388 URL: https://issues.apache.org/jira/browse/CONNECTORS-388 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi We have to try to upgrade the UI Crawler using Apache Velocity that a good solution that could fit with Manifold implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
[ https://issues.apache.org/jira/browse/CONNECTORS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188655#comment-13188655 ] Piergiorgio Lucidi commented on CONNECTORS-388: --- Created the branch to work on this issue: https://svn.apache.org/repos/asf/incubator/lcf/branches/CONNECTORS-388/ Upgrade the Crawler UI framework with Apache Velocity - Key: CONNECTORS-388 URL: https://issues.apache.org/jira/browse/CONNECTORS-388 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 72h Remaining Estimate: 72h We have to try to upgrade the UI Crawler using Apache Velocity that a good solution that could fit with Manifold implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
[
https://issues.apache.org/jira/browse/CONNECTORS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188697#comment-13188697
]
Piergiorgio Lucidi commented on CONNECTORS-388:
---
Started to work on this issue (r1233061).
I imported Apache Velocity in the lib folder and in the build files (Ant and
Maven), all the new dependencies are the following:
* antlr
* avalon
* jdom
* maven-ant-tasks
* oro
* werken-xpath
I had to update the Commons Collections dependencies from 2.1 to 3.2.1 that is
required in Velocity because it uses new classes introduced in the third
version of the library.
I updated the org.apache.manifoldcf.core.i18n.Messages class adding the new
method that must be used for all the connectors that must use Velocity
(outputResourceWithVelocity).
I started to work on the CMIS Connector, that's why I updated the
org.apache.manifoldcf.crawler.connectors.cmis.Message class that is related to
the specific connector.
To conform other connectors, it is only needed to change the method
outputResource to the new one outputResourceWithVelocity. And it is needed to
conform all the templates JS and HTML changing all the replacer from
${something:A} to $something:A, this because Velocity has a different way
to use replacers for parameters.
Now I have a problem to get load the HTML template in Velocity, in the Messages
class we have:
{code}
StringWriter stringWriter = new StringWriter();
try {
Velocity.mergeTemplate(resourceLoaderPath, UTF-8, context,
stringWriter);
}
catch (Exception e) {
throw new ManifoldCFException(e.getMessage(),e);
}
{code}
It seems that Velocity doesn't find for some reasons the template in the
classpath, notice that I'm using the ClasspathResourceLoader that is used for
this specific need:
{code}
Properties properties = new Properties();
properties.setProperty(VelocityEngine.RESOURCE_LOADER, classpath);
properties.setProperty(classpath.+VelocityEngine.RESOURCE_LOADER+.class,
ClasspathResourceLoader.class.getName());
{code}
So I think that we need only to solve this issue about classpath loading and we
have done!
Any hints?
Upgrade the Crawler UI framework with Apache Velocity
-
Key: CONNECTORS-388
URL: https://issues.apache.org/jira/browse/CONNECTORS-388
Project: ManifoldCF
Issue Type: Improvement
Components: Framework core
Affects Versions: ManifoldCF 0.3
Reporter: Piergiorgio Lucidi
Assignee: Piergiorgio Lucidi
Original Estimate: 72h
Remaining Estimate: 72h
We have to try to upgrade the UI Crawler using Apache Velocity that a good
solution that could fit with Manifold implementation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
[ https://issues.apache.org/jira/browse/CONNECTORS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188743#comment-13188743 ] Karl Wright commented on CONNECTORS-388: I'm refactoring the root build.xml to build up the manifest classpath a line at a time, so we'll have to merge that when the time comes. Other than that, good work! The reason that VelocityEngine doesn't find the resources is because they can only be accessed by the current classloader, which is defined in ManifoldCF core as a nested set of classloaders. But you can get the correct classloader using the method ManifoldCF.createResourceLoader(). Upgrade the Crawler UI framework with Apache Velocity - Key: CONNECTORS-388 URL: https://issues.apache.org/jira/browse/CONNECTORS-388 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 72h Remaining Estimate: 72h We have to try to upgrade the UI Crawler using Apache Velocity that a good solution that could fit with Manifold implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (CONNECTORS-389) Chemistry in-memory war renaming breaks mvn-bootstrap
Chemistry in-memory war renaming breaks mvn-bootstrap - Key: CONNECTORS-389 URL: https://issues.apache.org/jira/browse/CONNECTORS-389 Project: ManifoldCF Issue Type: Bug Components: Build Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Piergiorgio Lucidi Fix For: ManifoldCF 0.5 The recent renaming of the chemistry in-memory war broke the mvn-bootstrap scripts, which both have this in them: cmd /c mvn install:install-file -Dfile=lib/chemistry-opencmis-server-inmemory-war.war -DgroupId=org.apache.chemistry.opencmis -DartifactId=chemistry-opencmis-server-inmemory-war -Dversion=0.5.0 -Dpackaging=war -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
[ https://issues.apache.org/jira/browse/CONNECTORS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188843#comment-13188843 ] Karl Wright commented on CONNECTORS-388: I've had a look at what Velocity provides as far as resource loading options, and none of them are pertinent to ManifoldCF. So what we will need to do is extend the abstract base class org.apache.velocity.runtime.resource.loader.ResourceLoader. We'll also need to configure Velocity using something other than a Properties, since we'll need to instantiate our ManifoldCFResourceLoader class appropriately for the context we're in. I'm not quite sure how to do that yet. Upgrade the Crawler UI framework with Apache Velocity - Key: CONNECTORS-388 URL: https://issues.apache.org/jira/browse/CONNECTORS-388 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 72h Remaining Estimate: 72h We have to try to upgrade the UI Crawler using Apache Velocity that a good solution that could fit with Manifold implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
[ https://issues.apache.org/jira/browse/CONNECTORS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188853#comment-13188853 ] Karl Wright commented on CONNECTORS-388: It looks like we do not want to use the singleton approach to setting up Velocity, since you can only configure a singleton ONCE, and thus we won't be able to use different class loaders, which is essential. Instead, we'll need to set up a VelocityEngine object. It should be sufficient to create a single static VelocityEngine object in each connector's Messages class, which is configured to resolve resources based on that class's class loader. So the method in ui-core/i18n/Messages.java should accept a VelocityEngine argument in this model, and create a Velocity context for every template being rendered. I'm still not sure how to provide a VelocityEngine with an already-instantiated ResourceLoader class, but we should be able to figure that out looking at the Velocity source code. Upgrade the Crawler UI framework with Apache Velocity - Key: CONNECTORS-388 URL: https://issues.apache.org/jira/browse/CONNECTORS-388 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 72h Remaining Estimate: 72h We have to try to upgrade the UI Crawler using Apache Velocity that a good solution that could fit with Manifold implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1313#comment-1313 ] Hitoshi Ozawa commented on CONNECTORS-385: -- Great, but the Japanese characters in the site is still corrupted. Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hitoshi Ozawa updated CONNECTORS-385: - Attachment: end-user-documentation_ja_JP.html Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: end-user-documentation_ja_JP.html The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-388) Upgrade the Crawler UI framework with Apache Velocity
[ https://issues.apache.org/jira/browse/CONNECTORS-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1317#comment-1317 ] Karl Wright commented on CONNECTORS-388: r1233150 is the changes needed to get the model basically correct. Note that I haven't yet tried this setup; I have qualms about the VelocityEngine.setExtendedConfiguration() call, because I don't believe I've set all the pertinent defaults. But we shall see. Upgrade the Crawler UI framework with Apache Velocity - Key: CONNECTORS-388 URL: https://issues.apache.org/jira/browse/CONNECTORS-388 Project: ManifoldCF Issue Type: Improvement Components: Framework core Affects Versions: ManifoldCF 0.3 Reporter: Piergiorgio Lucidi Assignee: Piergiorgio Lucidi Original Estimate: 72h Remaining Estimate: 72h We have to try to upgrade the UI Crawler using Apache Velocity that a good solution that could fit with Manifold implementation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1318#comment-1318 ] Karl Wright commented on CONNECTORS-385: The site mirrors every 24 hours. Will take a bit longer to get out there. When it does you will need to refresh the pages in your browser to insure they aren't cached by your browser. Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: end-user-documentation_ja_JP.html The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CONNECTORS-385) Manifold CF site japanese is corrupted
[ https://issues.apache.org/jira/browse/CONNECTORS-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13188923#comment-13188923 ] Karl Wright commented on CONNECTORS-385: It has now updated. Manifold CF site japanese is corrupted -- Key: CONNECTORS-385 URL: https://issues.apache.org/jira/browse/CONNECTORS-385 Project: ManifoldCF Issue Type: Bug Components: Documentation Affects Versions: ManifoldCF 0.5 Reporter: Karl Wright Assignee: Karl Wright Fix For: ManifoldCF 0.5 Attachments: end-user-documentation_ja_JP.html The Japanese part of the site is corrupted when published. It seems that Forrest corrupts certain utf-8 characters. I've checked the latest Forrest and it doesn't help, so I've created FOR-1231 to track this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
