ADD about thesis's reference #113
Conversation
|
The doc of the "About reference" hasn't finish yet, I will add the detail of this chapter in a couple of days. |
|
It this ready for merge or still in development? |
| @@ -1,2 +1,2 @@ | |||
| % !Mode:: "TeX:UTF-8" | |||
| \chapter{模板代码实现} | |||
| % !Mode:: "TeX:UTF-8" | |||
There was a problem hiding this comment.
These two lines is ended with windows line break '\r\n' instead of unix style '\n' only.
You may need to change it in notepad++ or something like that.
|
Actually, this chapter is developing, But I don't know when will I finish it, so I pull it to the master branch of BUAAThesis in case of something like my file system is broke up. |
| @@ -75,8 +77,41 @@ \section{免责声明} | |||
| 任何组织或个人以本模板为基础进行修改、扩展而生成新模板，请严格遵守相关协议。 | |||
| 由于违反协议而引起的任何纠纷争端均与本模板编写者无关。 | |||
|
|
|||
| \section{本模板与教务处、研究生院所规定的论文格式要求的一些差异} | |||
There was a problem hiding this comment.
@huxuan 我在这儿加入这一section，你怎么看？
|
@JosephPeng 看了一下后面的内容，个人感觉意义不是很大，除了本科生那个硬性的区别（实际应该也不会很大，bibtex排出来的90%会比在word里人工按照那个所谓标准排出来的要“标准”），其他的不是因为官方本身的规定不清楚或者就是本身就有选择余地的要求。 这里我特别想引用一句话，“既然要用一个模板，就不要对它进行改动。”就像 @grissiom 同学之前说的那样，他基本是以我们的模板作为标准的。所以我们今后再处理issue时，应该先区分究竟是 bug 还是 problem，对于bug当然要修，对于problem尽可能给予hack的解决方案即可，对于像 @hellobiek 那样的热心用户，首先肯定是支持，而且要感谢他的热心反馈，确实有很多严重的问题我们之前没能发现。但是也要避免过于盲目满足个别用户的要求（我之前也犯过这个错）。 可以以1.0的发布为分水岭，在1.0版本发布之后，我建议对于代码修改的态度应该是能不修改就不修改，只有不得不修改的那种才是真正的bug。所以我们的模板和规定稍有不同是难免的，但没必要拉出来明说，就像我们以前讨论到的，这些不同不至于让谁不能毕业。 引用出处：http://bbs.ctex.org/forum.php?mod=redirect&goto=findpost&ptid=49871&pid=347056 |
|
@huxuan 你的意思是把“xxx的差别”那一节去掉？ |
|
可能我的想法有点偏激，我是觉得在我们保证模板没有太大问题的情况下，应该尽量减少这些可能的改变，不然会有很多更word风格的需求会提出来，应该让大家觉得，我们的模板就是对的，就应该是模板里面的风格即可(不影响毕设)，太多的可能性反而不利于模板本身的维护和推广。 |
|
我写出那些差异的话，相当于是给User一些他需要知道的(当然也可以不关心的)情况，告诉他使用本模板，将与规范有哪些地方有出入或有差别，并告诉user，使用本模板，绝大部分情况下是符合要求的。我认为给予user相应的知情权是必需的，而不是霸道的对user说“用这个模板就是对的，信不信由你，用不用由你”。 |
|
我比较赞同 @JosephPeng |
|
嗯，可能我又有点较真了，主要是觉得现在的doc越来越庞大了，但是可能更需要一个biref usage之类的东东，就象一般会议提供的latex模板本身自带的那个sample一样，毕竟很多人缺乏耐心去看生成的文档，而且的确需要一个简短的介绍来让user更直接更快捷的进入使用状态。 |
| \begin{minipage}[h]{.85\textwidth} | ||
| \zihao{-2}\heiti\centering{\buaa@thesissubtitle} | ||
| \end{minipage} | ||
| \vspace*{\stretch{1}} |
There was a problem hiding this comment.
@huxuan I don't know why there are so many differences in buaathesis cls, I didn't convert the file type, only change some places. Am I make some mistakes?
There was a problem hiding this comment.
@JosephPeng This problem usually caused by two reasons. The first is the change from utf8 to gbk or something else, the second tends to be the unix-style linebreak has been changed to windows style. This time the problem is caused by the second reason. I suggest you MUST look through all changes before each commit ESPECIALLY for push. If this kind of situation occured again, there must be something wrong with the code. So you should correct it before commit or push to avoid making the repo in a mess. I have already reset you last change which convert all unix-style linebreak to windows style and pushed the correct commit. If you still feel it hard to figure out the reason of this problem or the solution to solve this problem (only one command in linux terminal), do not be hesitate to tell me.
There was a problem hiding this comment.
@huxuan Thanks for your patientionful help, I would check it out next time and I wish I wouldn't make the same mistakes any more.
adjust the size of subtitle font in frontpage.
Add a beief introduction of the thesis's reference, and remove the blank page after the chapter Reference.